From: Jim Blandy <jimb@red-bean.com>
To: Keith Wright <kwright@tiac.net>
Cc: guile-gtk@sourceware.cygnus.com
Subject: Re: Towards guile-gtk 0.18
Date: Mon, 01 Nov 1999 06:37:00 -0000 [thread overview]
Message-ID: <m3vh7m1dn0.fsf@savonarola.red-bean.com> (raw)
In-Reply-To: <199910311854.NAA00327@kwright.tiac.net>
> > > Some historical perspective: people used to make fun of the Mach
> > > microkernel because it wasn't very "micro"
> >
> > > It turns out that a full half of the executable was due to
> > > automatically generated RPC stubs.
>
> Ouch! That hurts. I wrote that RPC stub generator. It seemed
> like a good idea at the time.
Sorry! I forget who it was who told me this. It was someone on the
Mach project at CMU, way back in 1990-92 or something.
next prev parent reply other threads:[~1999-11-01 6:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-10-24 13:14 Ariel Rios
1999-10-25 7:46 ` Miroslav Silovic
1999-10-25 10:55 ` Marius Vollmer
1999-10-25 14:45 ` Miroslav Silovic
1999-10-30 23:05 ` Jim Blandy
1999-10-31 4:34 ` Miroslav Silovic
1999-10-31 5:14 ` Marius Vollmer
1999-10-31 9:54 ` Keith Wright
1999-11-01 6:37 ` Jim Blandy [this message]
1999-11-02 21:42 ` Keith Wright
1999-11-13 7:42 ` Towards guile-gtk x.xx Daniel Skarda
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=m3vh7m1dn0.fsf@savonarola.red-bean.com \
--to=jimb@red-bean.com \
--cc=guile-gtk@sourceware.cygnus.com \
--cc=kwright@tiac.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 read-only IMAP folder(s) and NNTP newsgroup(s).