The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Dan Cross <crossd@gmail.com>
To: Andy Kosela <akosela@andykosela.com>
Cc: "tuhs@tuhs.org" <tuhs@tuhs.org>
Subject: [TUHS] Re: Early BSD license thread
Date: Thu, 22 Sep 2022 13:44:22 -0400	[thread overview]
Message-ID: <CAEoi9W5nA9q39reQqGFPM+oKQvgXGvpj5YgQLMvgkOs5EPkKMA@mail.gmail.com> (raw)
In-Reply-To: <CALMnNGgCmvd6b+ndW91VJj_KyHt=DY6jLrxT+YmAroZy_m7CEQ@mail.gmail.com>

On Thu, Sep 22, 2022 at 3:08 AM Andy Kosela <akosela@andykosela.com> wrote:
> On Thursday, September 22, 2022, Dan Cross <crossd@gmail.com> wrote:
>> On Wed, Sep 21, 2022 at 5:50 PM Phil Budne <phil@ultimate.com> wrote:
>> > Not to excuse the failure of the BSD team to properly attribute source
>> > origin by adding only their copyright notice, but didn't AT&T try
>> > unfair turnabout by not properly attributing the origins of their
>> > TCP/IP code?
>>
>> One of my favorite copyright notices was for /bin/true in System V.
>> An empty file got turned into 7 lines of comments holding copyright
>> boilerplate and an `#ident` line with an SCCS version number:
>> progress!
>
> That reminds me of the excellent dissertation of  Gerald Holzmann on Code Inflation[1].  The situation is even worse now and honestly I don't see it will improve in the future.  My take on the code inflation problem is that today without paid "volunteers" (from IBM, Oracle, Google, etc.) a large chunk of our modern software landscape would just collapse.  It is not 90s Internet anymore where hobbyists did it for fun, because frankly back then it was fun... Nowadays... not that much.

Indeed. Ted has made this point frequently; Linux for example
basically requires corporate sponsors to get new features into
the kernel. Sure, some individual might come up with a great
idea and implementation that'll make it in, but that's the exception
rather than the norm.

The flip side is that there's a lot of load-bearing infrastructure
that is barely maintained, if at all. This xkcd seems perennially
relevant: https://xkcd.com/2347/

I suppose the situation may be summed up as extremes at both
ends. In any event, it's not great.

        - Dan C.

  reply	other threads:[~2022-09-22 17:46 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-21 10:10 [TUHS] " Warner Losh
2022-09-21 12:36 ` [TUHS] " Rob Pike
2022-09-21 13:33   ` Marc Donner
2022-09-21 13:46   ` Warner Losh
2022-09-21 14:50     ` Rich Salz
2022-09-21 14:58       ` Warner Losh
2022-09-21 15:06         ` Miod Vallat
2022-09-21 14:57     ` [TUHS] Fwd: " Clem Cole
2022-09-21 15:09       ` [TUHS] " Larry McVoy
2022-09-21 15:25       ` Warner Losh
2022-09-21 22:06         ` [TUHS] " Bakul Shah
2022-09-21 22:20           ` Warner Losh
2022-09-21 21:14       ` [TUHS] Re: Fwd: " Theodore Ts'o
2022-09-21 21:46         ` Clem Cole
2022-09-21 21:49   ` [TUHS] " Phil Budne
2022-09-21 22:07     ` Rich Salz
2022-09-21 22:24       ` Warner Losh
2022-09-21 22:09     ` Dan Cross
2022-09-21 22:19       ` Steve Nickolas
2022-09-21 22:44         ` Joseph Holsten
2022-09-21 23:53           ` Chet Ramey
2022-09-22  0:32             ` Rob Pike
2022-09-22  7:08       ` [TUHS] " Andy Kosela
2022-09-22 17:44         ` Dan Cross [this message]
2022-09-22 18:44           ` [TUHS] " 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=CAEoi9W5nA9q39reQqGFPM+oKQvgXGvpj5YgQLMvgkOs5EPkKMA@mail.gmail.com \
    --to=crossd@gmail.com \
    --cc=akosela@andykosela.com \
    --cc=tuhs@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).