Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!ut-sally!husc6!mit-eddie!ll-xn!ames!sdcsvax!ucbvax!CAEN.ENGIN.UMICH.EDU!donp
From: donp@CAEN.ENGIN.UMICH.EDU (Don Peacock)
Newsgroups: comp.sys.apollo
Subject: Re: AEGIS/UN*X
Message-ID: <8706151345.AA03689@caen.engin.umich.edu>
Date: Mon, 15-Jun-87 09:45:41 EDT
Article-I.D.: caen.8706151345.AA03689
Posted: Mon Jun 15 09:45:41 1987
Date-Received: Sun, 21-Jun-87 02:12:30 EDT
Sender: daemon@ucbvax.BERKELEY.EDU
Distribution: world
Organization: The ARPA Internet
Lines: 65


In regard to :
       Dave Erstad (Erstad@HI-MULTICS.ARPA) writes:
 
           We've had half a dozen people working in the same general areas;
           frequently even had two people working on the same tool at the same time
           for different purposes; DSEE provides the ability to control
           interactions between these people to allow maximum sharing of
           commonality while preventing destructive interference.  It also allows
           alternate "branches" of development to proceed, so we may have an
           obsoleted version of a tool which we continue to bugfix, while
           developing the next generation of that tool.
 
       So?  We have a shell script which uses RCS to do all that stuff.  So what's
       the big deal?  My friends content that DSEE requires a server which eats up
       node cycles and VM space, is bulky and slow, and isolates the user in a
       subsystem that must be entered and exited.  Admittedly, this is all hearsay,
       since I've never used it myself.   But having used enough of the rest of the
       system to get a flavor of the things that Apollo provides, I would not be
       surprised.
       --
       Robert Reed, Tektronix CAE Systems Division, bobr@zeus.TEK

The next time you have several people working on thousands of lines of code
each at a different location and intend on turning your finished product
over to a support group try using DSEE.  With its history functions it allows
you to rebuild a system the way it was built 1,2 or 3 months ago or mix and 
match different versions of the same overall system.  A support person can
trace the development of a module from 0 lines to n lines and open up
the comments for each change which is a great help when fixing someone elses
code. I used this while working at General Motors and it is a GREAT HELP when 
you have something complex to code.
  

I have used APOLLO products which could have been easier to use or had bugs in them
but I've yet to see this OS everyone is comparing AEGIS to.  You know the
one, no bugs, great user interface, great development facilities, networking,
compatibility among differing machines...   OH you must be talking about
UN*X.  Thats right the perfect OS the one that is its own standard. The one overriding
+ that UN*X has that no other OS has is its ability to make programmers portable
other than that there is not a single thing that you can do with UN*x that some
other GURU in another OS can't do.  That is the reason that business is going to UN*X
not because its the greatest thing since sliced bread but because programmers and code
are portable to some extent.  Lets forget about the tools that are out there all the
don't run on the SUN either.

I use the C shell only!!!  I am forced to use /com commands at times when
nothing else is available ie. edacct edppo ... and we have close to 250 APOLLOs.


Mr. Reed
  Please next time you are listening to some hearsay sit down at your APOLLO
  take a week and learn for yourself what is useful and what isn't.  Don't
  believe everything you hear and please don't spread it around before
  you find things out for yourself.



sincerely:

Don Peacock (University of Michigan)


When I'm right nobody remembers,
When I'm wrong nobody fogets.