From: Otto Moerbeek <otto@drijf.net>
To: Mike Markowski <mike.ab3ap@gmail.com>
Cc: TUHS main list <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] screen editors / machine load
Date: Fri, 10 Jan 2020 14:56:45 +0100 [thread overview]
Message-ID: <20200110135645.GA47971@clue.drijf.net> (raw)
In-Reply-To: <CANq1pfn5ENTZVvZfH5F=6TOWc82txnTP9oZ5kwk6JGUjq8J-ew@mail.gmail.com>
On Fri, Jan 10, 2020 at 08:41:53AM -0500, Mike Markowski wrote:
> [2020-01-09 08:49] Dave Horsfall <dave@horsfall.org>
> > > I had a boss once who insisted that all his staff learn "ed",
> > > because one day it might be the only editor available; he was
> > > right...
> >
>
> I first used Unix on a pdp-11/70 in 1981, first year at university. My
> professor stopped by the computing center to see how his students were
> doing - super nice of him and a perk to pre-PC times! - and was showing me
> something or other regarding Unix. I had only used ed to that point and
> seeing him fire up vi was practically sci-fi to me. He showed me a few
> commands and vowed me to secrecy for fear if all students started using it,
> it would bring the 11/70 to its knees. Were multiple vi sessions really
> such a potential burden to the machine? I wouldn't think so with the slow
> nature of human i/o, yet there certainly were times when the pdp-11/70
> crashed as project due dates loomed closer and closer!
>
> Also, I very much enjoy this list. As an EE I use Unix-like OSes as a tool
> rather being a builder of the tool like many here. So I don't have the
> deep background to contribute to the collective history, but I'm on the
> sidelines enjoying the show. As a brief tie-in to the editor comparisons,
> I do a lot of DSP work for RF systems these days. Python makes it quick
> and easy to try new math, but has a maddening requirement that indentation
> be strictly tabs or strictly spaces. Text window pasting into a tab
> indented python file wreaks havoc. vim yank/put between split windows
> retains the type of white space and lets me use my vi muscle memory.
>
> Happy 2020,
> Mike Markowski
In my first year at university (1984) we had a VAX-11/750 running
4.1BSD with too many students. We had to switch to ex once in a while
to get any editing done. I believe it was not only vi itself that was
causing the load, it was also running many terminals in raw mode that
killed performance.
-Otto
next prev parent reply other threads:[~2020-01-10 14:03 UTC|newest]
Thread overview: 84+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-08 7:39 [TUHS] screen editors Thomas Paulsen
2020-01-08 15:58 ` Steve Nickolas
2020-01-08 23:41 ` Dave Horsfall
2020-01-09 1:43 ` Nemo Nusquam
2020-01-08 21:49 ` Dave Horsfall
2020-01-08 22:01 ` Clem Cole
2020-01-17 23:38 ` Dave Horsfall
2020-01-18 0:07 ` Ryan Casalino
2020-01-18 23:02 ` greg travis
2020-01-10 8:13 ` markus schnalke
2020-01-10 8:17 ` U'll Be King of the Stars
2020-01-11 19:58 ` markus schnalke
2020-01-11 20:54 ` Derek Fawcus
2020-01-11 21:27 ` Henry Bent
2020-02-04 8:40 ` Sijmen J. Mulder
2020-02-04 20:14 ` [TUHS] pronouncing *nix formulas (was: screen editors) G. Branden Robinson
2020-02-04 21:05 ` Dave Horsfall
2020-02-04 21:52 ` Derek Fawcus
2020-02-04 23:27 ` Rob Pike
2020-02-05 3:34 ` Warner Losh
2020-02-05 9:49 ` Angelo Papenhoff
2020-02-05 11:40 ` Rob Pike
2020-02-05 11:43 ` Brantley Coile
2020-02-05 10:58 ` Ralph Corderoy
2020-02-05 11:45 ` Rob Pike
2020-02-05 8:45 ` arnold
2020-02-05 13:35 ` Clem cole
2020-02-05 16:11 ` [TUHS] pronouncing *nix formulas Arthur Krewat
2020-02-05 16:16 ` Clem Cole
2020-02-05 17:05 ` Jon Steinhart
2020-02-05 17:09 ` Clem Cole
2020-02-08 3:31 ` Ronald Natalie
2020-02-08 4:19 ` Rob Pike
2020-02-11 1:16 ` George Michaelson
2020-02-11 6:38 ` Rob Pike
2020-02-05 20:26 ` David Arnold
2020-02-05 19:37 ` [TUHS] pronouncing *nix formulas (was: screen editors) Dave Horsfall
2020-02-05 19:57 ` Clem Cole
2020-02-05 20:50 ` Rob Pike
2020-02-05 21:43 ` Clem Cole
2020-02-05 21:59 ` Steve Nickolas
2020-02-05 22:22 ` Ed Carp
2020-02-06 2:43 ` Dan Cross
2020-02-06 3:00 ` Larry McVoy
2020-02-06 5:20 ` Vincenzo Nicosia
2020-02-06 14:54 ` Richard Salz
2020-02-06 15:10 ` [TUHS] pronouncing *nix formulas Lars Brinkhoff
2020-02-06 20:14 ` Dave Horsfall
2020-02-06 20:20 ` Warner Losh
2020-02-06 19:55 ` [TUHS] pronouncing *nix formulas (was: screen editors) Dave Horsfall
2020-02-06 21:48 ` Michael Parson
2020-02-06 23:56 ` Michael Parson
2020-02-06 22:17 ` Clem Cole
2020-02-07 0:21 ` [TUHS] finger usage (was: pronouncing *nix formulas (was: screen editors)) Greg 'groggy' Lehey
2020-02-07 0:27 ` Steve Nickolas
2020-02-07 0:54 ` [TUHS] finger usage (was: pronouncing *nix formulas Arthur Krewat
2020-02-07 1:00 ` Richard Salz
2020-02-07 5:26 ` Peter Jeremy
2020-02-07 4:31 ` [TUHS] finger usage (was: pronouncing *nix formulas (was: screen editors)) Dave Horsfall
2020-02-07 5:07 ` Greg 'groggy' Lehey
2020-02-07 5:39 ` Steve Nickolas
2020-02-07 21:39 ` Dave Horsfall
2020-02-07 16:14 ` Arthur Krewat
2020-02-07 22:37 ` Dave Horsfall
2020-02-07 4:23 ` Dave Horsfall
2020-02-06 2:23 ` [TUHS] pronouncing *nix formulas (was: screen editors) Dan Cross
2020-02-06 2:31 ` Dave Horsfall
2020-02-05 19:08 ` Dave Horsfall
2020-02-05 21:01 ` Nemo
2020-02-05 22:06 ` Dave Horsfall
2020-01-10 13:41 ` [TUHS] screen editors / machine load Mike Markowski
2020-01-10 13:56 ` Otto Moerbeek [this message]
2020-01-10 15:00 ` Mary Ann Horton
2020-01-10 15:48 ` Clem Cole
2020-01-10 22:18 ` Adam Thornton
2020-01-11 0:30 ` Christopher Browne
2020-01-10 15:31 ` [TUHS] screen editors Nemo Nusquam
2020-01-10 16:04 ` Clem Cole
2020-01-10 17:10 ` Dan Cross
2020-01-10 17:18 ` Steve Nickolas
2020-01-18 1:55 ` Michael Parson
2020-01-10 15:58 ` Theodore Y. Ts'o
2020-01-10 14:35 [TUHS] screen editors / machine load Noel Chiappa
2020-01-10 15:35 Noel Chiappa
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200110135645.GA47971@clue.drijf.net \
--to=otto@drijf.net \
--cc=mike.ab3ap@gmail.com \
--cc=tuhs@minnie.tuhs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).