From: erik quanstrom <quanstro@coraid.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Re: Novice
Date: Tue, 8 May 2007 09:27:34 -0400 [thread overview]
Message-ID: <4cb10edc5f742a2850beec63559426f7@coraid.com> (raw)
In-Reply-To: <1178628858.111317.26280@e65g2000hsc.googlegroups.com>
On Tue May 8 08:59:23 EDT 2007, isliguezze@gmail.com wrote:
> Thanks for the attention. I actually didn't mean it's simple, but
> It is elegant, because there is small amount of code, for example
> take 8 1/2 and X window systems - they both are graphical, though
> Plan9 graphics are a little bit strange, it is many times smaller in
> source...
the current system is "rio" --- a successor to 8½.
>
> Ken Thompson and Rob Pike say that UNIX(R) and all clones of it
> are ancient systems, Plan9 is modern; C language is bad, though
> Limbo is very good.
(prefaced with "as i see it".)
the basic problem with unix-type operating systems is they treat the
network in a fundamentally different way than they treat the filesystem.
network resources are named differently, use special-case file-descriptors, etc.
in linux that differences goes all the way down to the slab allocator.
there is no way to hand the vfs a socket buffer.
i don't think you can say "c is good, limbo is bad". they're different.
c is self-hosting. limbo is not.
- erik
prev parent reply other threads:[~2007-05-08 13:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-08 8:56 [9fans] Novice isliguezze
2007-05-08 9:14 ` Rogelio Serrano
2007-05-08 11:22 ` erik quanstrom
2007-05-08 12:59 ` [9fans] Novice isliguezze
2007-05-08 13:27 ` erik quanstrom [this message]
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=4cb10edc5f742a2850beec63559426f7@coraid.com \
--to=quanstro@coraid.com \
--cc=9fans@cse.psu.edu \
/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).