The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: kevin.bowling@kev009.com (Kevin Bowling)
Subject: Favorite UNIX
Date: Mon, 2 Oct 2017 04:52:41 -0700	[thread overview]
Message-ID: <CAK7dMtArd8jVmdt50hPU3DNZ9SQQWLoiPkjt3QCrwy5W2xFNjQ@mail.gmail.com> (raw)
In-Reply-To: <alpine.LRH.2.21.1710020135340.6255@waffle.shalott.net>

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

Bryan’s talks are unparalleled entertainment, but it’s hard for me not to
laugh at some of this with the benefit of more time passage.

There’s a lot of clean code worthy of inspection in Illumos, but I think
it’s bordering on the threshold of a historical project.  Key subsystems
like the VM and network stack have seen little development since 2009.  Sun
was a giant benevolent benefactor and nobody’s filled the void of working
on general infrastructure.

My gut feeling is Sun’s early ‘90s choices were inevitable death wish.
I’ve had the unsettling thoughts lately that Sun after this era was a
brilliant marketing company more so than anything else.

On Monday, October 2, 2017, <jason-tuhs at shalott.net> wrote:

>
>    > Solaris: so bad I left the company.
>>>
>>
> Why was Solaris so much worse than SunOS?
>>>
>>
> But that was a kick in the nuts to us engineers.  The sytem v source base
>> was crap compared to sunos, a huge step backwards.
>>
>> So my crowd pretty much all left in disgust.  There was a lot of
>> heartache over it.  None of us knew about the business deal at the time, in
>> fact I think a lot of management didn't know.
>> [...]
>> Instead, they repeated the SunOS journey.  Bryan and crew polished that
>> turd for years and got it sort of reasonable. [...] but they went for it
>> and got it better.  Only to have it tossed away again.  Yuck.
>>
>
> For anyone who hasn't seen it, there's a pretty good talk that gives the
> two-minute version of what Larry has described, and then picks up the story
> from there and runs with it over the next twentyish years:
>
> https://www.youtube.com/watch?v=-zRN7XLCRhc
>
>
>  -Jason
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20171002/81c05bcc/attachment.html>


  reply	other threads:[~2017-10-02 11:52 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-01 17:51 Noel Chiappa
2017-10-01 18:05 ` Larry McVoy
2017-10-01 18:39   ` Don Hopkins
2017-10-02  8:44   ` jason-tuhs
2017-10-02 11:52     ` Kevin Bowling [this message]
2017-10-02 14:17     ` Warner Losh
2017-10-01 18:13 ` Don Hopkins
2017-10-01 20:15 ` Steve Mynott
2017-10-01 21:21   ` Jon Steinhart
2017-10-01 23:28     ` Don Hopkins
2017-10-02  0:36     ` Larry McVoy
     [not found] <mailman.1424.1506881102.3779.tuhs@minnie.tuhs.org>
2017-10-01 19:09 ` Will Senn
  -- strict thread matches above, loose matches on Subject: below --
2017-09-29  2:58 [TUHS] " Kevin Bowling
2017-09-30 15:40 ` Michael Parson
2017-09-30 17:53   ` Ian Zimmerman
2017-09-30 18:34     ` Michael Parson
2017-09-30 18:45       ` Arthur Krewat
2017-10-01  0:36       ` Larry McVoy
2017-10-01  0:51         ` Dave Horsfall
2017-10-01  1:10           ` Larry McVoy
2017-10-01  1:13             ` Cory Smelosky
2017-10-01  3:43             ` Arthur Krewat
2017-10-01 14:07             ` Don Hopkins
2017-10-01  3:05       ` Michael Parson
2017-10-01  3:15         ` Kevin Bowling
     [not found]       ` <201710011513.v91FDSMB011831@freefriends.org>
2017-10-01 19:35         ` Michael Parson

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=CAK7dMtArd8jVmdt50hPU3DNZ9SQQWLoiPkjt3QCrwy5W2xFNjQ@mail.gmail.com \
    --to=kevin.bowling@kev009.com \
    /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).