From: "Iruata Souza" <iru.muzgo@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@9fans.net>
Subject: Re: [9fans] abaco @ plan9port [WAS: Hi and, plan9-native abaco sources?]
Date: Wed, 12 Mar 2008 13:55:52 -0300 [thread overview]
Message-ID: <d1c554290803120955y26edf96cu1d5bace928fd0b81@mail.gmail.com> (raw)
In-Reply-To: <f9648467cad047cb6c0fc84dec71b082@coraid.com>
On Wed, Mar 12, 2008 at 10:36 AM, erik quanstrom <quanstro@coraid.com> wrote:
> > I think this is a bad idea, what if you want to use an alternate
> > webfs (on a different NIC), or an non-standard cookies file? do you
> > want to wait whilst webcookies rescans it databse at startup and
> > webfs rescans its cache (work in progress)?
> >
> > If we continue this way why not put the code for webfs and and webcookies
> > in abaco, and why not include upas and nntpfs too; I guess you can see where
> > this is leading...
> >
> > I think fgb's simple shell script is an elegant solution, if this is what
> > you want (sh to rc translation not withstanding) but keeping webfs and webcookies
> > as long lived external servers has significant benefits - it is The plan9 way™
> > after all.
>
> standard slippery slope argument.
>
> i think that abaco (by inheratance from webfs) may confuse
> elegance with unfriendliness. for example, why do i have
> to type "http://"? why can't i type "g $query" to google
> something? why doesn't esc in the tag highlight like acme?
>
> abaco is great stuff. this is why i took the time to add a few
> of these things to my version. they might not be the height
> of elegance. they may not be added in the right place. perhaps
> webfs should do this. but usability is important, too.
>
have you sent your patches to fgb?
iru
next prev parent reply other threads:[~2008-03-12 16:55 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-11 22:29 philo
2008-03-11 23:44 ` Pietro Gagliardi
2008-03-12 12:05 ` Steve Simon
2008-03-12 13:36 ` erik quanstrom
2008-03-12 16:55 ` Iruata Souza [this message]
2008-03-12 17:22 ` erik quanstrom
2008-03-12 17:54 ` Federico G. Benavento
2008-03-12 18:54 ` Pietro Gagliardi
2008-03-12 18:59 ` erik quanstrom
2008-03-12 19:23 ` Federico G. Benavento
-- strict thread matches above, loose matches on Subject: below --
2008-03-12 23:08 erik quanstrom
2008-03-14 21:54 ` Bruce Ellis
2008-03-14 22:21 ` erik quanstrom
2008-03-08 3:00 [9fans] Hi and, plan9-native abaco sources? Sean Caron
2008-03-08 4:16 ` Iruata Souza
2008-03-10 11:38 ` Vinícius de Figueiredo Silva
2008-03-11 17:01 ` [9fans] abaco @ plan9port [WAS: Hi and, plan9-native abaco sources?] Enrico Weigelt
2008-03-11 17:12 ` Federico G. Benavento
2008-03-12 21:36 ` Enrico Weigelt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d1c554290803120955y26edf96cu1d5bace928fd0b81@mail.gmail.com \
--to=iru.muzgo@gmail.com \
--cc=9fans@9fans.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).