🚀 go-pugleaf

In article <4971@sdcsvax.UCSD.EDU> cooper@odin.ucsd.edu.UUCP (Ken Cooper) writes:
>In article <4849@ihlpf.ATT.COM> straka@ihlpf.UUCP (55223-Straka,R.J.) writes:
|| ...
|| ...
||For instance,
||do I really need to have ALL of the system and finder be memory resident?  Do
||I really need to have Cyrillic fonts (useless example, but you get the point)
||take up valuable memory if I only need them occasionally?  And, no, loading
||them occasionally with the font/da mover is not a solution, just a workaround.
|
|Try using Suitcase. 

Yes, but even that's a workaround!  (I assume) you have to still open the
font file manually every time you want to work on that file(s), or else
you are forced to place the fonts in the appropriate folder so that
Suitcase loads the fonts into the system heap at boot time anyway.  That is,
unless Suitcase was smart enough to figure out that a used font was not
system resident and go out and look for it.  Of course, that really belongs
in the domain of the system software anyway.

My point is that the operating system should take care of shielding these
sort of interactions from the user (and it does now, although in a
memory-hungry manner).  Tools like suitcase, f/da juggler+, et al. are very
useful tools, but are really patches (workarounds) since they don't solve this
original (memory-usage) problem.  (They do address OTHER, problems, of course!)
-- 
Rich Straka     ihnp4!ihlpf!straka

Advice for the day: "MSDOS - just say no."