[net.unix-wizards] TOPS-20 --> UNIX

BRITT@USC-ISIB.ARPA (09/27/83)

From:  Benjamin Britt <BRITT@USC-ISIB.ARPA>


Bill Rizzi has hit upon an interesting point.  Has anyone moved from
TOPS-20 to UNIX and liked it?  To be specific- does anyone believe he/she
is more productive working under UNIX after using TOPS-20?

-------

zornig%bbn-unix@sri-unix.UUCP (09/28/83)

From:  John Zornig <zornig@bbn-unix>

Sure, I have.  I used TOPS-20, and before that TOPS-10, for many years
before beginning with UNIX.  I can see that anyone who thinks that 
command completion and online help is the principal measure of an 
operating system or programming environment would love TOPS-20.  On 
the other hand, anyone who really uses the system, system calls and all,
could get real tired of TOPS-20 and BLISS.  I did.

Indeed, it was the severe shortcomings of TOPS-20 as a serious programming
environment that motivated a group at Yale to invest what seem like man-
centuries in developing the Yale Tools package.

If you want to see the difference, try writing your favorite UNIX utilities
in BLISS or MACRO-10 using TOPS-20 system calls and (echh..) byte pointers.
Don't forget 5 7-bit chars per word, left justified, and be sure to include
the precious command completion and "?" functions.

Talk's cheap....

				    John G. Zornig
				    Ye Olde Venerable
				      BBN Communications Corp.

dm%bbn-unix@sri-unix.UUCP (09/29/83)

From:  Dave Mankins <dm@bbn-unix>


I worked for a couple of years on TOPS-20 and its predecessor
TENEX before moving to UNIX.  I found UNIX to lead to a large
increase in my productivity almost immediately.  The big thing
that TENEX lacked that UNIX has is pipes and all the programs on
UNIX know how to use them--I spent a long time trying to teach a
large application program I was using to take it's input from
another process (since that time the application has been moved
off of TENEX and onto UNIX), and never really succeeded.  That
comes for free on UNIX.

Of course, we cheated at BBN and rewrote the terminal driver to
allow wakeup-sets and stop-at-the-bottom-of-the-page mode,
CRT-oriented erasing, etc. (this was back in the days of V6).
(Pipe everything through MORE? gag.  Build MORE into readnews and
news and the mail-reading program? double-gag.)

When my TOPS-20/TENEX friends ask me why I prefer UNIX, I tell
them about a 25-LINE LONG SHELL file I once wrote in about an
hour (I made lots of refinements) which goes and gets the past
few day's messages off of MIT-AI's bulletin board (running FTP
from a pipe, using AWK to generate FTP's command-input) and puts
them into uniquely-name files in a scratch directory, so I can
look at them at my leisure. 

How long do you think it would take to write a similar program on
TOPS-20?  I'd guess probably two or three days of very heavy
MACRO-10 hacking...Of course you'd probably never undertake the
task in the first place since it would seem so daunting. 

But it's true that there are lots of lessons that UNIX could
learn about paging, process-control, user-interface,
documentations, etc., etc., from TENEX, and MULTICS.  I was
struck by the initial responses to Scott Cooper's (?) article
("How long are we going to put up with this crap?"). 

The responses I mean are the ones of the "Oh, yeah?  Well name an
operating system that's better!"

About the ONLY operating system I've ever used with a worse user
interface and which was more poorly-documented than UNIX was
MIT's ITS system, which was abysmal in both those respects.  Come
on, folks, is UNIX the first "commercial-grade" operating system
you've ever used?  (ITS is by no means commercial-grade.)

There are some really neat ideas out there in OS land.  Don't
think UNIX has it all.  Look around a little. 

kg@hplabs.UUCP (09/29/83)

	Has anyone moved from TOPS-20 to UNIX and liked it?

Yes.
	To be specific- does anyone believe he/she is more productive working
	under UNIX after using TOPS-20?

Yes.

I work for a few years at school on TOPS-10.  When we got a V6 UNIX system
circa 1975 and put it up on an 11/34 I was blown away.  It was far more
powerful and easy to use than this 1 million dollar DEC-10.  Anytime
I have to use a -10 or -20 it's a royal pain.

The only thing I missed was command/filename recognition and completion...
so I implimented it (in a better manner than tenex or tops).
I've posted same to net.sources.

					Ken Greer
-- 
Ken Greer

SHAWN%mit-ml@sri-unix.UUCP (09/29/83)

From:  Shawn F. McKay <SHAWN@mit-ml>


I have, I still love lots of the things TOPS-20 does that UNIX does not, 
like command completion, and file name completion, but there is no reason
that if someone felt like it, unix could not do the same. the only thing
that unix could not do, is deal with '?' in the same manner, for, reasons
I need not mention to you folks.

But TOPS-20 was written for a different use I beleive. And it is my
opinion that BOTH are winning. But that UNIX SEEMS to do lots more then
tops-20. (but, when you look close, that works both ways, but for god's sake,
they are VERY different Operating Systems).

		Yours In Hacking(c),
		   -Shawn

CopyRight 1983, All Rights Reserved,

flamer@omsvax.UUCP (09/29/83)

The first OS I >ever< used was TOPS-10, followed by a slurry of DEC
OS's, then some Honeywell, CDC, and IBM.  I like Unix best.
(so there:  Nyahh nyahh!)

sundar@cwruecmp.UUCP (Sundar Iyengar) (09/29/83)

	I am headed the opposite way.  I have used UNIX for a
	few years now and I like it immensely.  Now I have to
	use TOPS-20 to complete course projects.  The only
	comment I have is that it is only unfortunate that
	we have to use TOPS-20.

	Sundar Iyengar
	sundar.Case@UDel-Relay
	decvax!cwruecmp!sundar

diamant@cwruecmp.UUCP (John Diamant) (09/29/83)

I have recently switched from TOPS-20 to UN*X (actually I still use TOPS
occasionally) -- I have found that the amount of time involved in
learning TOPS is much less than UN*X, mainly due to ? and ESC, but that
now that I know both, UN*X is definitely less intrusive (allows me to be
more productive).  I recently read a comment by someone in net.cog-eng
that UN*X is "expert-friendly" and I find that very fitting.

I would however like to point out that this discussion would be more
appropriate on net.cog-eng than net.unix-wizards.  I thus recommend that
all further discussion on this topic be confined to cog-eng.

					John Diamant
				Usenet: ...decvax!cwruecmp!diamant
				CSNet:  diamant@Case
				ARPA:   diamant.Case@UDel-Relay

roger@nmtvax.UUCP (10/02/83)

This message is empty.

gwyn%brl-vld@sri-unix.UUCP (10/03/83)

From:      Doug Gwyn (VLD/VMB) <gwyn@brl-vld>

?? TOPS-20 (aka TWENEX) is not the same as TOPS-10.

joe@fluke.UUCP (Joe Kelsey) (10/03/83)

You obviously missed the point completely - there is a WORLD of
difference between "Bottoms-10" and TOPS-20.  I wouldn't program on
"Bottoms-10" unless you really made it worth my while, although it is
an interesting dinosaur and also manages to support very large user
communities.  Quite simply, TOPS-20 provides the best environment for
everyone from novice to "hacker" that I have ever used.

/Joe Kelsey

FIGMO%kestrel@sri-unix.UUCP (10/04/83)

From:  Lynn Gold <FIGMO@kestrel>

May I remind you that not everyone who is on Unix-Wizards has access
to the Usenet and/or its mailing lists.  I, for one, am finding much
of this discussion pertinent to my applications.

--Lynn
-------
 

fulk@sunybcs.UUCP (Mark Fulk) (10/04/83)

Of great interest in this connection is the "TOOLS" project at Yale.
The authors (Ellis, van Leunen, Mishkin, Nix, et al) have replaced most
of the standard TOPS-20 utilities with their own and generally regularized
the TOPS-20 environment; they have made many of the potential capabilities
of the TOPS-20 kernel usable (background processes, etc.)  The main part
of the work seems to have been to replace TOPS-20 EXEC with their own version
(MUF, similar to the shell); to write a screen mode editor (Z), and to
provide mail and news systems.  They seem to have stolen from any source
with good ideas, mainly from UN*X, and my friends from Yale praise the
results to the skies.  Descriptions are available as Yale CS Dept.
tech reports nos. 231 and 232.