From: "Ronald G. Minnich" <rminnich@lanl.gov>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Some Plan9 questions
Date: Tue, 11 Feb 2003 15:55:26 -0700 [thread overview]
Message-ID: <Pine.LNX.4.44.0302111540440.6514-100000@carotid.ccs.lanl.gov> (raw)
In-Reply-To: <20030211223619.29018.qmail@scsi1.moonshynecomm.com>
On Tue, 11 Feb 2003, Matt Keeler wrote:
> 3) How hard is it for someone who is coming from a more common UNIX OS to
> get used to Plan9?
Speaking for me, there are at least 3 learning curves. Initially it's not
too bad (8c for cc, etc). Then you start trying to learn how to really use
the system, and learn how to use Acme etc., and unlearning all the dumb
things you learned to get used to Unix; e.g. getting used to using bind to
make it easy to build kernels without modifying the base kernel tree
(truthfully, how many of you out there started out using
disk/kfscmd allow
when you wanted to modify the kernel source? I happen to know one such
person who is now a prolific Plan 9 contributor ...)
The 3rd learning curve for me has been the steepest, trying to wrap my
brain around everything. Watching all the clever things people do.
Trying to set up a cpu cluster ...
Once you see all this stuff and go back to Unix, you keep saying "damn!
this is stupid! I wouldn't have this problem on Plan 9!". It's depressing
at times.
Oh yeah, program the graphics. You'll never want to touch X11 again.
Learn it well, it's worth it. The OS world by and large is not that
interesting right now, save for things like Plan 9.
ron
next prev parent reply other threads:[~2003-02-11 22:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <matt@ircguru.org>
2003-02-11 22:36 ` Matt Keeler
2003-02-11 22:50 ` Scott Schwartz
2003-02-11 22:55 ` Ronald G. Minnich [this message]
2003-02-12 18:32 ` north_
2003-02-12 18:38 ` George Gensure
2003-02-12 18:52 ` northern snowfall
2003-02-12 23:40 ` George Gensure
2003-02-13 0:05 ` northern snowfall
2003-02-11 23:25 ` Russ Cox
2003-02-12 0:13 ` Russ Cox
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=Pine.LNX.4.44.0302111540440.6514-100000@carotid.ccs.lanl.gov \
--to=rminnich@lanl.gov \
--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).