Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: Notesfiles $Revision: 1.6.2.17 $; site ea.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!mhuxj!ihnp4!inuxc!pur-ee!uiucdcs!ea!mwm
From: mwm@ea.UUCP
Newsgroups: net.arch
Subject: Re: Re: B1700
Message-ID: <800006@ea.UUCP>
Date: Sun, 28-Oct-84 23:58:00 EST
Article-I.D.: ea.800006
Posted: Sun Oct 28 23:58:00 1984
Date-Received: Thu, 1-Nov-84 03:40:32 EST
References: <486@ccice2.UUCP>
Lines: 20
Nf-ID: #R:ccice2:-48600:ea:800006:000:1058
Nf-From: ea!mwm    Oct 28 22:58:00 1984

/***** ea:net.arch / watdcsu!herbie /  2:38 am  Oct 25, 1984 */
You say MVS was slower than CP/M, which I agree with, but not having the
tools may be inaccurate.  Having been a systems programmer in an MVS
environment, I know that approximately half the really useful tools are
kept hidden, on principle from the general user.
/* ---------- */

The tools I was talking about: Visual editors with split-screen & multiple
buffers (the universities 4.2 system has one - I put it there so I wouldn't
have to put up with (ugh) vi); a reasonable selection of programming
languages - LISP, C, FORTRAN, COBOL, ALGOL, Pascal; a symbolic debugger
that worked at the language level, not the assembler level; text formatters
that knew something about the structure of a document (think Scribe & TEX);
graphics hardware other than bogosity on the line printer; typesetting
software to use said hardware; communications software; probably others
that I've forgotten. Something tells me that these aren't the tools that
are being hidden from me by the MVS wizards.

	<mike