Computer Old Farts Forum
 help / color / mirror / Atom feed
From: davida at pobox.com (David Arnold)
Subject: [COFF] Standing on the shoulders of giants, free or not
Date: Wed, 19 Feb 2020 15:38:37 +1100	[thread overview]
Message-ID: <FFC78AB8-E4AF-4B11-B1AA-BA86DBE6115A@pobox.com> (raw)
In-Reply-To: <20200219025616.GE30841@mcvoy.com>

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

> On 19 Feb 2020, at 13:56, Larry McVoy <lm at mcvoy.com> wrote:
> On Tue, Feb 18, 2020 at 09:27:47PM -0500, Clem Cole wrote:

<…>

>> Certainly, for us that lived in a 'pre-UNIX' world, UNIX was a huge
>> success.   It did what we wanted -- it displaced the proprietary systems.
>> And in the end, the UNIX ideas and UNIX technologies live today - because
>> they were open and available to everyone.    It does not matter if it was
>> GPL'ed or otherwise.
> 
> I agree with that.

This “displacement” has really only been widely true in the last 5-10 years.

“Open Systems” seemed to peak (from my recollection) around the early 90’s.  The Unix model and POSIX APIs became dominant, and VMS, NonStop, MVS, VM, etc, etc, died away, often together with their hardware.  The exception to this was Windows NT (and descendants) which killed the Open System era, and dominated the small to mid-size markets, leaving Open Systems and the remnants of proprietary OSes to large and/or specialised niches.

One factor behind the success of Windows Server was that the PC hardware market’s brutal competition led to decent quality hardware at a fraction of the price of competing platforms.  This overwhelmed the advantages of Open Systems, and the movement stalled — people were willing to buy into a proprietary OS again, because it was *cheap*, despite just recently having escaped OS lock-in with Open Systems.

Concurrent with the rise of Windows was the emergence of Linux (and early on, the *BSDs).  The PC Unices (including Linux) leveraged the PC platform like Windows did.  But it was the dotcom era, and the availability of dirt cheap virtual hosts that had to run Linux because the licensing cost of Windows Server was an order of magnitude more than the virtual hardware, which has resulted in Linux (and thus POSIX APIs and a Unix model) being almost ubiquitous today.

I think it’s a mistake to conflate Open Systems with Free/Open Source Software.  Despite eg. POSIX being the root of both, Open Systems was dead in the market well before FOSS operating systems took off outside academic environments.




d




  reply	other threads:[~2020-02-19  4:38 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-18 21:17 clemc
2020-02-18 22:58 ` tytso
2020-02-19  1:18   ` clemc
2020-02-19  1:54   ` lm
2020-02-19  2:27     ` clemc
2020-02-19  2:56       ` lm
2020-02-19  4:38         ` davida [this message]
2020-02-19  5:04       ` tytso
2020-02-19  6:11       ` imp
2020-02-19  7:56         ` wkt
2020-02-19 21:21           ` dave
2020-02-19 15:19         ` lm
2020-02-19 21:13           ` clemc
2020-02-19 21:37           ` dave
2020-02-19  2:41   ` dave
2020-02-19  8:27 ` thomas.paulsen

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=FFC78AB8-E4AF-4B11-B1AA-BA86DBE6115A@pobox.com \
    --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).