🚀 go-pugleaf

In article <76000176@uiucdcsp> gillies@uiucdcsp.cs.uiuc.edu writes:
>
>You may argue that UNIX is easier to program.  That's because you're
>probably writing lousy code.  Sure, you can write lousy code on
>the macintosh and life is just as easy.  Never assume you run out
>of anything, and your code will be truly *simple*.
>
>The Macintosh is built so that you implement contingencies when
>resources get low.  I believe that many parts of UNIX (stdio) are not.
>They just assume it's fine to crash the process.
>Don Gillies {ihnp4!uiucdcs!gillies} U of Illinois

Hmmm - well, I do know that I tried vainly to implement a very large
database for the A/UX project using Excel. The database was every single
command, system call, subroutine, and file with an attached description
and origin etc. Excel couldn't even begin to handle it, nor could any of the
other spreadsheets or database packages available through the Apple internal
software library. So I went back to using awk and vi. (ugh - vi 700,000 lines
sometimes ...).

I wanted the Mac superior look and feel, but gee whiz, far too many mac
programs have horrible limitations compared to the "lousy" UNIX programs
Don complains (??) about.

I.e., I disagree with Don. There are limitations, but I'll take a limit
of say 50MB swap space for a virtual UNIX system over a 1/2/4 MB Mac OS
heap/stack limit any day.
-- 
-------------------------------------------------------------------------------
Philip K. Ronzone, A/UX Technical Manager                   APPLELINK: RONZONE1
Apple Computer, Mail Stop 27AJ, 10500 N. DeAnza Blvd.  Cupertino, CA  95014
UUCP:  ...!{sun,voder,nsc,mtxinu,dual,unisoft}!apple!phil