The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Christopher Browne <cbbrowne@gmail.com>
To: Rob Pike <robpike@gmail.com>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] V9 shell [was Re: Warner's Early Unix Presentation]
Date: Tue, 11 Feb 2020 13:35:07 -0500	[thread overview]
Message-ID: <CAFNqd5VvUFre1gFKwd9CgMWY_z-+Ji_r5e7Nv0Z4Cez+1-M69g@mail.gmail.com> (raw)
In-Reply-To: <CAKzdPgz6qPuqOfTe4eLqmM4f4RXTxqWRO-3NLHTaMxJg7mT-Nw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2010 bytes --]

On Tue, 11 Feb 2020 at 05:00, Rob Pike <robpike@gmail.com> wrote:

> My general mood about the current standard way of nerd working is how
> unimaginative and old-fashioned it feels. There are countless ways we could
> be interacting with our terminals, editors, and shells while we program,
> but for various sociological and historical reasons we're pretty much using
> one from decades ago. I'm sure it's productive for almost everyone, but it
> seems dull to me. We could be doing something much more dynamic. I mean,
> xterm is hardly more sophisticated than the lame terminal code that ran in
> mpx (ca. 1982), other than colors and cursor addressing, which date from
> the 1960s via early PCs. IDEs don't sing to me, although they are powerful,
> because they don't integrate well with the environment, only with the
> language. And they are just lots of features, not a coherent vision. No
> model to speak of.
>
> Compare what happened with our shell windows with what happened with our
> "smart" phones in the last 20 years and you'll get some inkling of what I
> think we're missing. It's not that we should program the way we use
> iPhones, but that there are fields where user interface work has made a
> real different recently. Not so in programming, though. We're missing out.
>
> But I'm a grumpy old man and getting far off topic. Warren should cry,
> "enough!".
>

I recently saw indication that the UI for Sam and Acme were inspired by
Oberon.  (And per url [1] below, Rob Pike is quoted, sort of...)

I'd be interested (and I think that's a TUHS thing ;-) ) in hearing some
elaboration on that.  All that is said is that "Rob was blown away" and
that this "influenced" Sam/Acme; is there some further explanation of that
worth pointing at?  (Or are some Oberon fans putting words in mouths?  ;-) )

[1] https://lists.inf.ethz.ch/pipermail/oberon/2011/006245.html
-- 
When confronted by a difficult problem, solve it by reducing it to the
question, "How would the Lone Ranger handle this?"

[-- Attachment #2: Type: text/html, Size: 2630 bytes --]

  parent reply	other threads:[~2020-02-11 18:35 UTC|newest]

Thread overview: 61+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-07 22:25 [TUHS] Warner's Early Unix Presentation Warren Toomey
2020-02-07 23:57 ` Rob Pike
2020-02-08  0:43   ` Warren Toomey
2020-02-08  3:37     ` Warner Losh
2020-02-08 15:15   ` Warner Losh
2020-02-08 21:50     ` Rob Pike
2020-02-08 22:29       ` Chet Ramey
2020-02-08 22:54         ` Rob Pike
2020-02-08 23:02           ` Chet Ramey
2020-02-08 23:11             ` Rob Pike
2020-02-08 23:13               ` Rob Pike
2020-02-08 23:21               ` Kurt H Maier
2020-02-08 23:26                 ` Rob Pike
2020-02-08 23:28                   ` Chet Ramey
2020-02-08 23:26               ` Chet Ramey
2020-02-08 23:29                 ` Rob Pike
2020-02-08 23:35                   ` Warner Losh
2020-02-08 23:36                   ` Chet Ramey
2020-02-08 23:54                     ` Rob Pike
2020-02-09  0:11                       ` Chet Ramey
2020-02-09  0:19                   ` Larry McVoy
2020-02-08 22:31       ` Richard Salz
2020-02-10 13:18       ` Tony Finch
2020-02-10 15:05       ` Dan Cross
2020-02-10 15:46         ` [TUHS] V9 shell [was Re: Warner's Early Unix Presentation] arnold
2020-02-10 18:39           ` Rob Pike
2020-02-10 18:59             ` Bakul Shah
2020-02-10 19:58             ` Angelo Papenhoff
2020-02-10 20:11               ` Chet Ramey
2020-02-11  9:33             ` arnold
2020-02-11  9:47               ` Noel Hunt
2020-02-11  9:47               ` Rob Pike
2020-02-11  9:59                 ` Rob Pike
2020-02-11 17:05                   ` Steffen Nurpmeso
2020-02-11 17:18                     ` Arthur Krewat
2020-02-11 18:22                     ` Kurt H Maier
2020-02-16 21:34                       ` Wesley Parish
2020-02-11 18:26                     ` Jon Steinhart
2020-02-11 23:56                       ` Steffen Nurpmeso
2020-02-12  0:12                         ` Jon Steinhart
2020-02-12  1:03                           ` [TUHS] V9 shell Warren Toomey
2020-02-12  5:54                           ` [TUHS] V9 shell [was Re: Warner's Early Unix Presentation] Rob Pike
2020-02-11 17:36                   ` Dan Cross
2020-02-11 18:35                   ` Christopher Browne [this message]
2020-02-11 18:54                     ` Rob Pike
2020-02-11 21:36                     ` Harald Arnesen
2020-02-11  3:32 Doug McIlroy
2020-02-11  3:53 ` Larry McVoy
2020-02-11 11:24   ` Ralph Corderoy
2020-02-11 15:51     ` Larry McVoy
2020-02-11  4:46 ` Warren Toomey
2020-02-11  5:12   ` Steve Nickolas
2020-02-11  6:33 ` Rob Pike
2020-02-11  9:40 ` arnold
2020-02-11 15:06   ` Chet Ramey
2020-02-11 14:36 ` Clem Cole
2020-02-11 15:29   ` Mike Markowski
2020-02-11 16:03   ` Bakul Shah
2020-02-11 17:12     ` Clem Cole
2020-02-11 17:17     ` Steve Nickolas
2020-02-11 17:21 ` Dan Cross

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=CAFNqd5VvUFre1gFKwd9CgMWY_z-+Ji_r5e7Nv0Z4Cez+1-M69g@mail.gmail.com \
    --to=cbbrowne@gmail.com \
    --cc=robpike@gmail.com \
    --cc=tuhs@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).