Path: utzoo!utgpu!jarvis.csri.toronto.edu!helios.physics.utoronto.ca!ists!yunexus!davecb From: davecb@yunexus.UUCP (David Collier-Brown) Newsgroups: comp.arch Subject: Re: the Multics from the black lagoon :-) Message-ID: <7479@yunexus.UUCP> Date: 12 Feb 90 13:22:41 GMT References: <8859@portia.Stanford.EDU> <20571@watdragon.waterloo.edu> Organization: York U. Computing Services Lines: 39 In article <1990Feb7.221800.804@utzoo.uucp> henry@utzoo.uucp (Henry Spencer) writes: | Remember that Multics and OS/360 are the two classic examples of second- | system effect (overconfidence after a successful first system leads to | vast complexity and a union-of-all-wishlists approach on the second). pcg@rupert.cs.aber.ac.uk (Piercarlo Grandi) writes: | To put Multics and OS/360 in the same phrase is offensive. | Multics was very clearly designed to be as orthogonal and lean as | possible, and it largely succeeded. The overconfidence was in | breaking a lot of new ground, not in the inexistent morass of | features. It was a research project after all. I have to disgree with both of you here! Multics really was "designed", (as opposed to OS/360, which was accreted), and it was an unusual act at the time to set out the goals and algorithms that were to be used to achieve them in formal research papers beforehand. [ref: (a) the MIT Multics papers, various ACM articles (b) personal communication, one of the designers of CICS) Multics was supposed to be a production-quality computing service, thus the name "MULTiplexed Computing Service". It was by no means a research project. That it was not a research project annoyed Honeywell (who loved GCOS) no end, leading to the strange algorithm: if year % 2 then announce cancellation of Multics else announce next release of Multics --dave -- David Collier-Brown, | davecb@yunexus, ...!yunexus!davecb or 72 Abitibi Ave., | {toronto area...}lethe!dave Willowdale, Ontario, | Joyce C-B: CANADA. 416-223-8968 | He's so smart he's dumb.