Computer Old Farts Forum
 help / color / mirror / Atom feed
From: clemc at ccc.com (Clem Cole)
Subject: [COFF] Standing on the shoulders of giants, free or not
Date: Tue, 18 Feb 2020 21:27:47 -0500	[thread overview]
Message-ID: <CAC20D2PPYA87KMNSYJQxCfhuubYKQDLc-HRsTHt05U07m9TvPQ@mail.gmail.com> (raw)
In-Reply-To: <20200219015446.GC30841@mcvoy.com>

I'm not 100% sure why I'm arguing other than I feel this is so wrong and so
disingenuous to those that came before.
But, you have to decide that having access to all your sources for your
system is your measure of 'success.'  My value of success is no more VMS,
Kronos, or VM/CMS or the like.   I will accept Larry's position that he had
many roadblocks that were often silly.   But I really don't think my world
was as 'charmed' as he claims and his was quite as bad as his might think
you look at it.

That said, we have deviated from what it means to be "open."  What I'm
hearing from Ted and Larry that they think open can only mean stallman's
definition.  I have said, that is not, was not the original definition, nor
is it the only case and that the UNIX technology itself was really not as
tied up as he claims.  I think Larry did have access to sources (maybe not
at his University), but like so many of us, once he got to a place that had
them (like SGI or Sun).  My point is that besides being to read about it in
books and papers, getting access to the source from AT&T or UCB was really
the norm and stating otherwise is disingenuous and trying to rewrite
history a bit.

A point Ted has made and I accept is by the time of the UNIX Wars, the old
proprietary folks were trying to keep their own versions of UNIX 'secret'
and to use Larry terms those roadblocks to >>there<< code was real.  But
the truth is that the AT&T codebase (while getting more and more expensive
as the HW dropped in cost), was always available, and people both
commercial and research had it.

The problem was that as hardware cost dropped, more and more people wanted
the sources too and that were the I think the difference in the success
metrics come.

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.

In the end, what matters to me is the ideas, the real intellectual property
NOT the source that implements it.    This has been proven within the UNIX
community too many times.  It has been re-engineered so many times over.
Just like Fortran lives today, although it's different from what I learned
in the 1960s.  It's still Fortran.   Unix is different from what I saw in
the early 1970s, but its still Unix.

And that is because the *ideas that makeup what we call UNIX ARE open* and
the people looked at the sources, looked at the papers, talked to each
other and the community built on it.

It looks like a duck.  It quacks like a duck and even tastes like duck
(mostly) when you inside.   It's a duck.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/coff/attachments/20200218/8a6a3a40/attachment.html>


  reply	other threads:[~2020-02-19  2:27 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 [this message]
2020-02-19  2:56       ` lm
2020-02-19  4:38         ` davida
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=CAC20D2PPYA87KMNSYJQxCfhuubYKQDLc-HRsTHt05U07m9TvPQ@mail.gmail.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).