Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!mips!pacbell.com!ucsd!nosc!baron!ryptyde!dant
From: dant@ryptyde.UUCP (Daniel Tracy)
Newsgroups: comp.sys.amiga.advocacy
Subject: Re: De-macification of the Amiga (Re: The Amiga's Future)
Keywords: Future, Amiga, etc.
Message-ID: <95@ryptyde.UUCP>
Date: 23 Jun 91 01:53:35 GMT
References: <73@ryptyde.UUCP> <1991Jun20.160550.27873@mintaka.lcs.mit.edu> <81@ryptyde.UUCP> <1991Jun22.020815.233@Sugar.NeoSoft.com>
Reply-To: dant@ryptyde.UUCP (Daniel Tracy)
Organization: Ryptyde Timesharing (ryptyde.cts.com)
Lines: 13

Responding to the following:

"Since with shared libraries and shared text the application itself is
usually small, this is rarely a problem. Certainly you can run more programs
on an Amiga than on a Mac with the same amount of RAM."

Can you explain to me what shared libraries are? It sounds to me like
object-oriented code that is sharable across applications. That would
be interesting. Basically follows the same philosophy of resources,
eh? I don't agree with your last statement at all. Various resources
aren't loaded into memory until they're needed, and if there isn't 
enough room, some more resources are purged. Resources are also, then,
a sort of quasi-Virtual Memory that we've had since 1984.