The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: lm@mcvoy.com (Larry McVoy)
Subject: [TUHS] Why Linux not another PC/UNIX [was Mach for i386 ...]
Date: Wed, 22 Feb 2017 13:34:05 -0800	[thread overview]
Message-ID: <20170222213405.GJ9439@mcvoy.com> (raw)
In-Reply-To: <CAC20D2MK=hrhYP=AQn4PKZMXt_KLPCZu4R+D+FOuXLLPssiecw@mail.gmail.com>

On Wed, Feb 22, 2017 at 02:35:00PM -0500, Clem Cole wrote:
> > I found routines
> > that were bit for bit identical in both in less than 5 minutes.  The one
> > I remember was bmap(), I found a couple of others that I don't remember
> > (just remember there were more) and I gave up in disgust.  I was pretty
> > disappointed that CSRG considered this not AT&T source, it was.
> >
> ???Agreed... the argument... I'm not saying it was correct... was that the
> code for bmap and like was the obvious code and any reasonable programmer
> would have written it that way.???  

So suppose you owned a software company and someone had a source license,
rewrote some of the code and claimed the rest was obvious so it didn't
need to be rewritten.  Now your code is out there for free.  Affecting
your revenue stream.  How well is that "any reasonable programmer
would have written it that way" going to play with with you?  

You are an experienced guy, you know that any reasonable programmer would
have written the very same initial version of your code but that's not
what you shipped.  You shipped debugged, tuned code.  It was debugged
and tuned through years of experience with users, that takes time.
I find it really really hard to swallow that any reasonable programmer
would come up with the same code in a vacuum.

I'll remind you I'm deep into the source management world and I've
repeatedly seen my own engineers want to rewrite code and what do they
want to write?  What was checked in as version 1.1.  All the warts are
from real world experience and they want to get rid of them (until 
they look at the history and understand why the warts are there).

I'd argue that what you'd get from any reasonable programmer is the
naive initial version that works in theory but fails in practice.

In my mind, the BSD guys cheated.  If it were my code, if I owned
that and they tried to make that argument, yeah, I'd sue them as well.
AT&T messed up the suit but I don't think they were wrong.  IP counts
for something, it's expensive to fix all those bugs, it's cheap to do
the initial naive implementation.

Morally, in my mind, BSD was tainted.  Whether it was proven so in a
court of law doesn't change my opinion.  It was AT&T's code to release,
yes, I wanted them to do so as well, but it's their code.  Just 
because we think it should free doesn't make it morally right to
make it be free.  Doing so is theft in my book.

And for the record, I've seen the same behaviour in Linux.  There 
was wholesale copying of BSD licensed drivers and other code into
the kernel, some mumbles about it being dual licensed, but eventually
it became GPL only.  That's theft as well in my opinion.

Perhaps my ethics are a bit too rigid, but they are my ethics and
aren't likely to change.


  parent reply	other threads:[~2017-02-22 21:34 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-22  3:38 Clem Cole
2017-02-22  4:28 ` Dan Cross
2017-02-22 15:36   ` Clem Cole
2017-02-22 16:11     ` Larry McVoy
2017-02-22 17:00       ` Clem Cole
2017-02-22 17:06         ` Chet Ramey
2017-02-22 18:24         ` Larry McVoy
2017-02-22 19:35           ` Clem Cole
2017-02-22 20:18             ` arnold
2017-02-22 22:11               ` Clem Cole
2017-02-22 21:34             ` Larry McVoy [this message]
2017-02-22 22:56               ` Clem Cole
2017-02-22 23:13                 ` Larry McVoy
2017-02-22 23:51                   ` Clem Cole
2017-02-22 23:51           ` Paul Ruizendaal
2017-02-23 19:15             ` Clem Cole
2017-02-23 20:31               ` Random832
2017-02-23 22:48                 ` Joerg Schilling
2017-02-24  2:07                   ` Jason Stevens
2017-02-23 23:06                 ` Wesley Parish
2017-02-22 17:41       ` Arthur Krewat
2017-02-22 21:00     ` Michael Kerpan
2017-02-22 22:03       ` Arno Griffioen
2017-02-22 22:51         ` Larry McVoy
2017-02-22 23:29         ` Clem Cole
2017-02-23  4:53           ` Gregg Levine
2017-02-22 22:18       ` Clem Cole
2017-02-24  3:53     ` Dan Cross
2017-02-22  5:56 ` Steve Nickolas
2017-02-24  5:31   ` John Labovitz

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=20170222213405.GJ9439@mcvoy.com \
    --to=lm@mcvoy.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).