Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!cmcl2!rutgers!ames!xanth!kyle
From: kyle@xanth.UUCP (Kyle Jones)
Newsgroups: comp.arch,comp.unix.wizards,comp.os.misc
Subject: Re: Big Programs Hurt Performance
Message-ID: <2501@xanth.UUCP>
Date: Sun, 20-Sep-87 15:44:33 EDT
Article-I.D.: xanth.2501
Posted: Sun Sep 20 15:44:33 1987
Date-Received: Sun, 20-Sep-87 22:58:06 EDT
References: <1665@ncr-sd.SanDiego.NCR.COM) <8579@utzoo.UUCP) <6886@eddie.MIT.EDU) <14888@topaz.rutgers.edu>
Lines: 17
Keywords: cost of bloated programs
Xref: mnetor comp.arch:2269 comp.unix.wizards:4365 comp.os.misc:201

In <14888@topaz.rutgers.edu>, hedrick@topaz.rutgers.edu (Charles Hedrick) sez:
> You don't really want the window system in ROM.

You're right.  I typed "ROM" but I was thinking of protected RAM.
I certainly don't want a buggy window system burned into ROM for
posterity.

> What you really want is shared libraries.  That way, only one copy
> of the code is shared by all programs that use it, but you can
> change it.

This doesn't sound much different from the current scheme.  The
advantage of having the window system in protected RAM is that you
don't have gargantuan executables for small programs; calls to system
tools are simply linked to their known entry points in memory.

Please explain more about shared libraries.