From: Roman Shaposhnik <rvs@sun.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] crosstool fails on gentoo
Date: Mon, 2 Jun 2008 15:32:46 -0700 [thread overview]
Message-ID: <1212445966.4280.1097.camel@work.sfbay.sun.com> (raw)
In-Reply-To: <5d375e920806021337m51160c64rf20e0e1f96aca522@mail.gmail.com>
On Mon, 2008-06-02 at 22:37 +0200, Uriel wrote:
> He was boasting about how wonderful it was to be able to debug and
> profile stuff with this huge kernel hack (third biggest subsystem in
> the Solaris kernel, forgot exactly how many, but a few hundred
> thousand lines of code). In the end to do stuff 99% of which can be
> done in Plan 9 with iostat and acid, and the other 1% can be done with
> print statements and careful thought.
>
> But no, he told me, they needed this whole new layer of complexity
> (IIRC it includes even a bytecode interpreter/compiler inside the
> kernel), because I didn't understand how hard it had become to debug
> software this days, you had a bug, and you had to go from apache, to
> the Java Application Server, to Oracle, to the file system, etc, etc.
> millions and millions of lines of code, and it had become impossible
> to debug or profile applications anymore, because the issue could be
> anywhere in this huge stack... so what they do? they add *yet another
> layer of complexity so you can look at all that stuff at the same
> time*.
>
> And even more funny was to see the BSD and Lunix folks falling all
> over themselves to be the first ones to get the same thing for their
> systems.
DTrace is an interesting example. I'd be the first one to agree with
you, if it wasn't for the fact that it *is* useful for *me*. It just
is. And it is useful at exactly the right level -- the level of a
simple tool. Like awk or sed. Its like a protective suit for
walking in sh^H^Hmud -- all I care about is that it doesn't leak
and doesn't make me sweat. If its engineering is complex -- well,
it has to interface with that gooey stuff on the outside after all.
I think I'll drop this analogy now (too much worrying about ISS
and the little accident that they almost had there) but I hope
you'll get the idea?
Of course, I'd much rather use Plan9 and not need that kind of
technology. The guy was right, thought. unless Oracle gets ported
to Plan 9 (and somehow magically gets cleansed along the way) there's
no way for the simple sane system to shine. I guess it really is
a bit of chicken and the egg problem.
> The idea of simple and sane interfaces between simple and carefully
> designed components is totally lost, it is all about extensibility
> (XML!) and 'standards' (more XML!), and if you want to make things
> faster, of course the solution is to add a huge layer of caches and
> other magic...
Agreed 100%
> (I still laugh every time I think of distcc)
I don't understand this point. Would you like it better it was a
services you get out of nodes who export their "compile/link"
interface into your namespace?
> But enough ranting and rambling for today, just remember what Gordon
> Bell said, because nobody else will:
>
> "The cheapest, fastest, and most reliable components are those that
> aren't there."
Couldn't agree more!
Thanks,
Roman.
next prev parent reply other threads:[~2008-06-02 22:32 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <483D8DBE.4090005@cableone.net>
[not found] ` <200805282337.11349.yann.morin.1998@anciens.enib.fr>
2008-06-01 15:12 ` Enrico Weigelt
2008-06-02 19:25 ` Uriel
2008-06-02 19:55 ` ron minnich
2008-06-02 19:57 ` erik quanstrom
2008-06-02 20:09 ` Eric Van Hensbergen
2008-06-02 20:37 ` Uriel
2008-06-02 20:45 ` erik quanstrom
2008-06-02 21:00 ` Uriel
2008-06-02 22:32 ` Roman Shaposhnik [this message]
2008-06-02 23:00 ` Iruata Souza
2008-06-02 23:21 ` ron minnich
2008-06-03 0:50 ` Iruata Souza
2008-06-03 0:54 ` erik quanstrom
2008-06-03 2:02 ` Nick LaForge
2008-06-05 11:11 ` Enrico Weigelt
2008-06-05 11:21 ` Bruce Ellis
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=1212445966.4280.1097.camel@work.sfbay.sun.com \
--to=rvs@sun.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).