Computer Old Farts Forum
 help / color / mirror / Atom feed
From: david at kdbarto.org (David)
Subject: [COFF] Other OSes?
Date: Thu, 5 Jul 2018 14:25:38 -0700	[thread overview]
Message-ID: <C82653D8-8577-46C1-B0E6-8378ACA6DA5C@kdbarto.org> (raw)
In-Reply-To: <82df833ae2a587b386b4154fc6051356a3510b19@webmail.yaccman.com>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 3558 bytes --]

I find that anything I have to do twice winds up in a shell script, on the assumption that I’ll do it again. So I’ve written a lot of scripts lately, mostly to automate some tools to run our software validation system. These aren’t long (10-15 lines) and I freely give them to others knowing that they will either ignore it (mostly) or use it as is without ever looking at the internals.

I think that editor scripts have died out. ed is almost designed for scripting, and with vi, emacs, and other GUI based editors the concept of scripting the editor has died away. Sad, I do remember writing some really hairy ed scripts.

A quick read of Hank Levy’s book (thanks for the link) brings back (somewhat bad) memories of working on the iAPX 432. I found the chip interesting in concept, and poorly suited for what the company wanted done. Trying to fold the software to fit the hardware didn’t work out. The project was abandonded.

	David

> On Jul 5, 2018, at 1:49 PM, Steve Johnson <scj at yaccman.com> wrote:
> 
> That's an interesting topic, but it also gets my mind thinking about UNIX features that were wonderful but didn't evolve as computers did.
> 
> My two examples of this are editor scripts and shell scripts.   In the day, I would write at least one shell script and several editor scripts a day.  Most of them were 2-4 lines long and used once.  But they allowed operations to be done on multiple files quite quickly and safely.
> 
> With the advent of glass teletypes, shell scripts simply evaporated -- there was no equivalent.  (yes, there were programs like sed, but it wasn't the same...).  Changing, e.g., a function name oin 10 files got a lot more tedious.
> 
> With the advent of drag and drop and visual interfaces, shell scripts evaporated as well.   Once again, doing something on 10 files got harder than before.   I still use a lot of shell scripts, but mostly don't write them from scratch any more.
> 
> What abstraction mechanisms might we add back to Unix to fill these gaps?
> 
> Steve
> 
> 
> 
> ----- Original Message -----
> From: "Clem Cole" <clemc at ccc.com>
> To:"Bakul Shah" <bakul at bitblocks.com>
> Cc:<coff at tuhs.org>
> Sent:Thu, 5 Jul 2018 11:23:04 -0400
> Subject:Re: [COFF] Other OSes?
> 
> 
> 
> 
> On Thu, Jul 5, 2018 at 2:40 AM, Bakul Shah <bakul at bitblocks.com <mailto:bakul at bitblocks.com>> wrote:
> On Jul 4, 2018, at 10:56 PM, Warren Toomey <wkt at tuhs.org <mailto:wkt at tuhs.org>> wrote:
> > 
> > OK, I guess I'll be the one to start things going on the COFF list.
> > 
> > What other features, ideas etc. were available in other operating
> > systems which Unix should have picked up but didn't?
> > 
> > [ Yes, I know, it's on-topic for TUHS but I doubt it will be for long! ]
> 
> - Capabilities (a number of OSes implemented them -- See Hank Levy's book:
>   https://homes.cs.washington.edu/~levy/capabook/ <https://homes.cs.washington.edu/~levy/capabook/>
> - Namespaces (plan9)
> 
> ​+1 for both​
> 
> 
> _______________________________________________
> COFF mailing list
> COFF at minnie.tuhs.org <mailto:COFF at minnie.tuhs.org>
> https://minnie.tuhs.org/cgi-bin/mailman/listinfo/coff <https://minnie.tuhs.org/cgi-bin/mailman/listinfo/coff>
> 
> ᐧ
> _______________________________________________
> COFF mailing list
> COFF at minnie.tuhs.org
> https://minnie.tuhs.org/cgi-bin/mailman/listinfo/coff

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/coff/attachments/20180705/da57f067/attachment.html>


  reply	other threads:[~2018-07-05 21:25 UTC|newest]

Thread overview: 61+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-05  5:56 wkt
2018-07-05  6:29 ` spedraja
2018-07-05  6:40 ` bakul
2018-07-05 15:23   ` clemc
2018-07-05 20:49     ` scj
2018-07-05 21:25       ` david [this message]
2018-07-06 15:42         ` gtaylor
2018-07-05 22:38       ` ralph
2018-07-05 23:11       ` bakul
2018-07-06  0:06         ` lm
2018-07-06 15:49           ` gtaylor
2018-07-06  0:52       ` tytso
2018-07-06  5:59         ` ralph
2018-07-06 15:59           ` gtaylor
2018-07-06 16:10             ` ralph
2018-07-06 16:47               ` gtaylor
2018-07-06 15:57         ` gtaylor
2018-07-06 15:38       ` gtaylor
2018-07-09  1:56         ` tytso
2018-07-09  3:25           ` gtaylor
2018-07-09  3:35             ` crossd
2018-07-09  3:43               ` gtaylor
2018-07-09  3:52                 ` imp
2018-07-09 11:32                   ` perry
2018-07-09 11:50                     ` perry
2018-07-09 11:34                 ` crossd
2018-07-09  5:23             ` tytso
2018-07-09 12:52               ` clemc
2018-07-09 13:06                 ` [COFF] PiDP Obsolesces Guaranteed clemc
2018-07-09 14:39                 ` [COFF] Other OSes? tytso
2018-07-09 14:46                   ` clemc
2018-07-09 11:24           ` perry
2018-07-05 22:51   ` ewayte
2018-07-08 20:31   ` perry
2018-07-08 20:53     ` perry
2018-07-09  2:44     ` crossd
2018-07-10  5:30       ` bakul
2018-07-16 14:49         ` crossd
2018-07-16 16:59           ` [COFF] Capabilities (was " bakul
2018-07-06  0:55 ` [COFF] " crossd
2018-07-06  5:42   ` bakul
2018-07-09  2:51     ` crossd
2018-07-10  5:41       ` bakul
2018-07-06  4:04 ` grog
2018-07-06 16:10   ` gtaylor
2018-07-06 18:27     ` [COFF] Editor Scripts scj
2018-07-06 19:04       ` gtaylor
2018-07-08 20:50 ` [COFF] Other OSes? perry
2018-07-08 23:27   ` bakul
2018-07-09  0:00     ` grog
2018-07-09  0:13       ` perry
2018-07-09  0:05     ` crossd
2018-07-09  0:56       ` lm
2018-07-09  2:23         ` crossd
2018-07-09  0:11     ` perry
2018-07-09  0:19       ` crossd
2018-07-09  2:00         ` bakul
2018-07-09  3:02           ` [COFF] Origination of awful security design [COFF, COFF] bill
2018-07-09 13:10           ` [COFF] Other OSes? david
2018-07-09 13:17           ` perry
2018-07-09 13:13         ` perry

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=C82653D8-8577-46C1-B0E6-8378ACA6DA5C@kdbarto.org \
    --to=coff@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).