The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: "G. Branden Robinson" <>
Subject: [TUHS] Re: AIX moved into maintainance mode (fwd)
Date: Thu, 19 Jan 2023 14:54:24 -0600	[thread overview]
Message-ID: <20230119205424.hjs32x2a3aq2rlzy@illithid> (raw)
In-Reply-To: <>

[-- Attachment #1: Type: text/plain, Size: 1358 bytes --]

At 2023-01-19T20:21:30+0000, segaloco via TUHS wrote:
> In my own internal narrative at least, my stance is BSD is UNIX moreso
> than not in that the code may have changed, there may not even be a
> lick of AT&T in there (not true, handful of files, SCO lawsuit, etc.),
> but it's still UNIX in design, much more than say something like Linux
> could be considered.  It's like if some architect inherited the Empire
> State Building but was then told you can only do anything with it if
> you replace everything.
> In the end, it's still going to be different than taking a plot of
> land and deciding, hey, I want to build something like the Empire
> State Building.  In the former sense, you can start to replace the
> windows, then the door, then the elevators, etc etc, over time, you
> see a gradual transition of A into B, which leads to unmistakable
> vestiges since they were actively being worked around and within in
> the replacement process.

Engineers who (stereotypically) disdain the study of humanities seem
frequently to discover the Ship of Theseus problem.  ;-)

Maybe TOG has the best approach after all; if your supercargo can pony
up the gold and your pilot can navigate your craft between Scylla and
Charybdis, you get to call it the Ship of Theseus, even if many others
are afloat.  :D


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      reply	other threads:[~2023-01-19 20:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-19 20:08 Steve Nickolas
2023-01-19 20:21 ` segaloco via TUHS
2023-01-19 20:54   ` G. Branden Robinson [this message]

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20230119205424.hjs32x2a3aq2rlzy@illithid \ \ \

* 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).