Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!uakari.primate.wisc.edu!aplcen!haven!decuac!hussar.dco.dec.com!mjr
From: mjr@hussar.dco.dec.com (Marcus J. Ranum)
Newsgroups: comp.unix.programmer
Subject: Re: Why use U* over VMS
Message-ID: <1990Oct17.211857.19213@decuac.dec.com>
Date: 17 Oct 90 21:18:57 GMT
References: <16438@shlump.nac.dec.com>
Sender: news@decuac.dec.com (Network News)
Reply-To: mjr@hussar.dco.dec.com (Marcus J. Ranum)
Organization: Digital Equipment Corp., Washington Ultrix Resource Center
Lines: 23

In article <16438@shlump.nac.dec.com> heintze@fmcsse.enet.dec.com (Siegfried Heintze) writes:

>So, assuming VAXset is part of the VMS environment, what makes U* better?
>(Feel free to answer in the context of "money is of no concern" as well as
>"money is significant").

	As a pure development environment, none is better than whatever
one you're most familiar with.

	When I did [uck!] some coding on PCs, I used a toolkit that hid
the PC from me by making it look Unix-like. If I do development on VMS,
I'll try to work from within Eunice. Not because one or the other is
inherently *better*, but because Unix is what I know best. [I happen to
have learned Unix in preference to everything else because the way it
works resonates nicely with the way I think] This argument cuts both
ways, of course.

	The big benefit I think a lot of people see in Unix is that it
offers the *potential* for a high degree of portability (inter vendor,
inter platform, inter O/S - sometimes) if due care is taken. This makes
a *BIG* difference if "money is significant" is the answer.

mjr.