Path: utzoo!attcan!uunet!nih-csl!lhc!ncifcrf!haven!aplcen!samsung!cs.utexas.edu!hellgate.utah.edu!uplherc!giga!unislc!dgb
From: dgb@unislc.uucp (Douglas Barrett)
Newsgroups: comp.sys.mac.misc
Subject: Re: UNIX is yuck (was Re: Next intro...)
Message-ID: <1990Oct22.145918.725@unislc.uucp>
Date: 22 Oct 90 14:59:18 GMT
References: <1990Oct16.173634.20494@smsc.sony.com>
Organization: Unisys, SLC Utah
Lines: 35

From article <1990Oct16.173634.20494@smsc.sony.com>, by dce@smsc.sony.com (David Elliott):
> 
> In article <1990Oct11.220943.9764@unislc.uucp>, dgb@unislc.uucp (Douglas Barrett) writes:
> |> If we compare os to os.  UNIX is more complicated.  It takes more hardware
> 
> Interesting.  I would have said exactly the opposite.
> 
> Unix was designed to be simple.
> [...]
> The Mac, on the other hand, is complex.  Each program must handle much
> more of the "os" type of operations, dealing with a more complicated
> filesystem and memory model.

If you take stuff out of the os and put in a user program the os gets
simpler and the program more complicated, no?  This implies moving
things from a user program to the os makes the os more complicated,
no?

>[stuff about ptys and sockets]

Yes, code is code once you understand it.  But as any Mac hack will tell
you adding ipc (which the Mac has none of), multitasking (*I* don't think
the Mac has), paged vertual memory (...), buffered io (...), and multiuser 
capabilities (...) *does* make the os more complicated.  You will discover
this if and when Mac ever has an os which does these things.  I mean the
Mac os fits in 1/2M of ROM, no?  The kernel on the machine I am working on
now has ~2M data/stack/bss, and about 15M by time you alloc all of the
data structures.

You were joking right?  Just pulling my chain?

-------------------------------------------------------------------------
Douglas Barrett                                   I speak for myself
Unix Systems Programmer
Unisys SLC Utah