From: David Leimbach <leimy2k@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Pegasus 2.6 is released
Date: Mon, 2 Feb 2009 15:18:53 -0800 [thread overview]
Message-ID: <3e1162e60902021518n2e04fd55xca863f92bb99f7c9@mail.gmail.com> (raw)
In-Reply-To: <509071940902021430i95a4eclbc8350611ff12a4b@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1047 bytes --]
On Mon, Feb 2, 2009 at 2:30 PM, Anthony Sorace <anothy@gmail.com> wrote:
> erik wrote:
>
> > it's interesting to compare this with the sleezy not-paths
> > that e.g. gnome programs can take, like uris. great as long
> > as long as you don't care to use anything but gnome tools.
>
> i had that debate with a kde-loving linux admin. i had been explaining
> why plan 9 was interesting or significant, and he countered with the
> kde example. i was marginally impressed by the number of protocols
> they handled, but when i asked how you'd use it with cat and friends,
> he said "no, just use kate".
>
> i reeled, stuttered, tried to get out something that sounded like
> "layering violation", and ran away. it wasn't even a cost/benefit
> argument; there wasn't any recognition of the costs.
>
> Right but when you consider KDE runs on windows, then it's not as much of a
layering violation... no more than Java is I guess anyway.
The layering violation that I usually point at is the /dev/tcp created by
the bash shell :-).
[-- Attachment #2: Type: text/html, Size: 1443 bytes --]
next prev parent reply other threads:[~2009-02-02 23:18 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-01 4:29 Kenji Arisawa
2009-02-01 4:41 ` lucio
2009-02-01 4:47 ` Kenji Arisawa
2009-02-01 4:43 ` John Barham
2009-02-01 4:50 ` andrey mirtchovski
2009-02-01 5:47 ` John Barham
2009-02-01 6:44 ` erik quanstrom
2009-02-01 7:27 ` John Barham
2009-02-01 11:12 ` Francisco J Ballesteros
2009-02-01 12:56 ` erik quanstrom
2009-02-02 19:25 ` sqweek
2009-02-02 19:44 ` erik quanstrom
2009-02-02 19:49 ` Roman V. Shaposhnik
2009-02-02 21:22 ` John Barham
2009-02-02 21:27 ` erik quanstrom
2009-02-02 21:32 ` David Leimbach
2009-02-02 22:11 ` Roman V. Shaposhnik
2009-02-02 22:17 ` erik quanstrom
2009-02-02 22:30 ` Anthony Sorace
2009-02-02 22:44 ` erik quanstrom
2009-02-02 22:57 ` Anthony Sorace
2009-02-02 23:04 ` Bruce Ellis
2009-02-03 4:26 ` lucio
2009-02-03 4:43 ` Bruce Ellis
2009-02-03 6:38 ` ron minnich
2009-02-02 23:18 ` David Leimbach [this message]
2009-02-02 22:12 ` ron minnich
2009-02-02 22:14 ` erik quanstrom
2009-02-02 22:32 ` ron minnich
2009-02-02 22:34 ` erik quanstrom
2009-02-02 22:18 ` Roman V. Shaposhnik
2009-02-02 22:22 ` Francisco J Ballesteros
2009-02-02 22:30 ` Roman V. Shaposhnik
2009-02-03 10:55 ` Richard Miller
2009-02-03 16:03 ` ron minnich
2009-02-03 16:07 ` erik quanstrom
2009-02-03 16:48 ` ron minnich
2009-02-03 17:01 ` erik quanstrom
2009-02-02 22:07 ` Roman V. Shaposhnik
2009-02-01 7:31 ` [9fans] Dynamic loading et al (Was: Pegasus 2.6 is released) lucio
2009-02-01 17:26 ` ron minnich
2009-02-01 18:42 ` lucio
2009-02-01 20:14 ` ron minnich
2009-02-01 18:04 ` Dave Eckhardt
2009-02-01 18:39 ` lucio
2009-02-01 11:26 ` [9fans] Pegasus 2.6 is released Charles Forsyth
2009-02-01 11:56 ` lucio
2009-02-01 13:02 ` erik quanstrom
2009-02-02 17:38 ` John Barham
2009-02-02 17:48 ` ron minnich
2009-02-01 4:50 Kenji Arisawa
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=3e1162e60902021518n2e04fd55xca863f92bb99f7c9@mail.gmail.com \
--to=leimy2k@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).