Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watmath!clyde!rutgers!mit-eddie!uw-beaver!tektronix!teklds!zeus!bobr
From: bobr@zeus.UUCP
Newsgroups: comp.sys.apollo
Subject: Re: AEGIS/UN*X
Message-ID: <1827@zeus.TEK.COM>
Date: Wed, 10-Jun-87 16:41:49 EDT
Article-I.D.: zeus.1827
Posted: Wed Jun 10 16:41:49 1987
Date-Received: Sat, 13-Jun-87 07:02:20 EDT
References: <870609130948.836911@HI-MULTICS.ARPA>
Reply-To: bobr@zeus.UUCP (Robert Reed)
Organization: CAE Systems Division, Tektronix Inc., Beaverton OR
Lines: 20

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