The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Larry McVoy <lm@mcvoy.com>
To: Theodore Ts'o <tytso@mit.edu>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Re: Fwd: [simh] Announcing the Open SIMH project
Date: Sun, 5 Jun 2022 18:15:11 -0700	[thread overview]
Message-ID: <20220606011511.GG10240@mcvoy.com> (raw)
In-Reply-To: <Yp1LLxvqGV4hFkBN@mit.edu>

On Sun, Jun 05, 2022 at 08:32:47PM -0400, Theodore Ts'o wrote:
> An interesting question is if CSRG had been actively pushing the state
> of the art foreward, would that have provided sufficient centripetal
> force to keep the HP/UX, SunOS, DG/UX, etc., from spintering?  After
> all, it's natural to want to get a competitive advantage over your
> competition by adding new features --- this is what I call the "Legacy
> Unix value-add disease".  But if you can't keep up with the upstream
> developments, that provides a strong disincentive from making
> permanent forks.  For that matter, why was it that successive new
> releases of AT&T System V wasn't able to play a similar role?  Was it
> because the rate of change was too slow?  Was it because applications
> weren't compatible anyway due to ISA differences?  I don't know....

I think I know but my opinion is very Sun centric.  Sun was the innovator
of the the time.  NFS, RPC, VM system that replaced the buffer cache so
everything was just pages, read/write/map, all the same pages.  Sun had
critical mass in talent and they innovated.  Everyone else followed
Sun (and hated them for it).

AT&T, other than the original group that did Unix, didn't innovate much
in the Unix domain.  SysV was sort of meh compared to SunOS.  When Unix
was sort of a skunk works, tons of good stuff happened.  When corporate
took it over, it became less interesting.  There was some good stuff, I
liked the document work bench stuff, I liked learn(1), it wasn't all bad.
But it wasn't even close to the same pace of innovation that Sun had,
I'm super grateful to have been at Sun while that was happening, that's
a once in a lifetime experience.

AT&T did fund Plan 9, if I remember history correctly, so that was 
a step back towards the original Unix innovation team.  I really wanted
plan 9 to take over but AT&T kept it away from open source too long and
Linux was too entrenched.  Classic Betamax vs VHS, the less good answer
won.  Sigh.

> So from a computer science point of view, one could argue that NetBSD
> was "better", and that Linux had a whole bunch of hacks, and some
> might even argue was written by a bunch of hacks.  :-)  However, from
> the user's perspective, who Just Wanted Their Laptop To Work, the fact
> that Linux had some kind of rough PCMCIA support first mattered a lot
> more than a "we will ship no code before its time" attitude.  And
> some of those users would become developers, which would cause a
> positive feedback loop.

I think "it just works" is key.  Linux was really competing with Windows
and Linus knew that.  He could have cared less about *BSD, they just
weren't on his radar screen.  But Windows was.  Very early versions
of RedHat were good enough on the install that you could just tab your
way through it.  I remember being impressed because I was installing a
machine that didn't have a mouse (yet) and I just tabbed my way through
it and it was fine.

Today's FreeBSD install process is like a trip back to 1980.  It is
not pleasant.  The Linux install process 15 years ago was a better
experience than Windows install process (if you've done the windows
install then get some ethernet dongle that windows recognizes so you can
connect to the internet, then do the driver search and install, install,
install all the drivers - contrast that with Linux where it just has 99%
of the drivers in the kernel).

"It just works" for the win.

  parent reply	other threads:[~2022-06-06  1:15 UTC|newest]

Thread overview: 58+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <BCDAF4C4-12EC-49D6-84A6-4592E245922F@comcast.net>
     [not found] ` <CAC20D2NGMK1NG3J+iR8t2rAzOc2uWCe9ZGRJzkZn6ECgMETJEQ@mail.gmail.com>
     [not found]   ` <CAC20D2OK9muQm=gCSeRzarV_HQF6vZ9VNuYRas4uCbMyxYKjJA@mail.gmail.com>
2022-06-03 20:00     ` [TUHS] " Clem Cole
2022-06-03 20:12       ` [TUHS] " Blake McBride
2022-06-03 20:23       ` G. Branden Robinson
2022-06-03 21:06         ` Clem Cole
2022-06-03 21:20           ` Tom Ivar Helbekkmo via TUHS
2022-06-03 21:32             ` Larry McVoy
2022-06-03 21:34               ` Tom Ivar Helbekkmo via TUHS
2022-06-03 21:37                 ` Larry McVoy
2022-06-03 21:36               ` Tom Ivar Helbekkmo via TUHS
2022-06-03 21:40                 ` Larry McVoy
2022-06-03 22:16                   ` Tom Ivar Helbekkmo via TUHS
2022-06-03 22:30                     ` Larry McVoy
2022-06-03 22:52                       ` Warner Losh
2022-06-03 23:48                         ` Larry McVoy
2022-06-04  0:10                           ` Warner Losh
2022-06-04  1:05                             ` Larry McVoy
2022-06-04  1:46                               ` David Arnold
2022-06-06  0:32                               ` Theodore Ts'o
2022-06-06  0:47                                 ` George Michaelson
2022-06-06  1:17                                   ` Larry McVoy
2022-06-06  1:02                                 ` Warner Losh
2022-06-06  1:09                                 ` Dan Cross
2022-06-06  1:15                                 ` Larry McVoy [this message]
2022-06-06  1:40                                   ` Dan Cross
2022-06-06  2:36                                     ` Larry McVoy
2022-06-06 12:43                                       ` Dan Cross
2022-06-06 13:41                                         ` Larry McVoy
2022-06-06 14:27                                           ` Blake McBride
2022-06-06 14:33                                             ` Steve Nickolas
2022-06-06 14:53                                     ` Henry Bent
2022-06-06 23:28                                       ` David Arnold
2022-06-07 14:30                                     ` Theodore Ts'o
2022-06-07 15:08                                       ` Dan Cross
2022-06-07 15:25                                         ` Larry McVoy
2022-06-07 16:03                                           ` Will Senn
2022-06-07 16:38                                             ` Warner Losh
2022-06-07 16:45                                               ` Larry McVoy
2022-06-07 16:57                                                 ` Warner Losh
2022-06-07 17:05                                                   ` Larry McVoy
2022-06-07 16:46                                               ` Blake McBride
2022-06-07 17:26                                                 ` Paul Winalski
2022-06-07 20:09                                                   ` Blake McBride
2022-06-07 17:00                                               ` Paul Winalski
2022-06-07 23:41                                                 ` [TUHS] " Chris Hanson
2022-06-07 15:55                                         ` [TUHS] Re: Fwd: " Richard Salz
2022-06-03 23:56                         ` David Arnold
2022-06-04  0:30                           ` Yeechang Lee
2022-06-04  1:03                             ` Adam Thornton
2022-06-03 22:33                     ` Warner Losh
2022-06-03 22:40                       ` Tom Ivar Helbekkmo via TUHS
2022-06-03 22:56                         ` Warner Losh
2022-06-03 22:26               ` Warner Losh
2022-06-03 22:19             ` Warner Losh
2022-06-03 21:35         ` Ben Walton
2022-06-03 20:52       ` Will Senn
2022-06-03 21:06         ` [TUHS] " Adam Thornton
2022-06-04  9:09           ` Ralph Corderoy
2022-06-04  2:59 [TUHS] Re: Fwd: " Bakul Shah

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=20220606011511.GG10240@mcvoy.com \
    --to=lm@mcvoy.com \
    --cc=tuhs@tuhs.org \
    --cc=tytso@mit.edu \
    /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).