From: "Theodore Ts'o" <firstname.lastname@example.org>
To: David Arnold <email@example.com>
Cc: segaloco <firstname.lastname@example.org>,
Joseph Holsten <email@example.com>,
Subject: [TUHS] Re: [OT?] 1993 'Sourceware' paper anniversary. What was right & any surprises?
Date: Thu, 10 Nov 2022 01:14:35 -0500 [thread overview]
Message-ID: <Y2yWy8BYFxFiIy4D@mit.edu> (raw)
On Thu, Nov 10, 2022 at 12:28:49PM +1100, David Arnold wrote:
> > On 10 Nov 2022, at 11:47, segaloco via TUHS <firstname.lastname@example.org> wrote:
> > What I find incredibly interesting any time the concept of
> > fragmentation comes up is how did several versions of UNIX with
> > slightly differing interfaces create such a headache for UNIX
> > vendors and users in the day, but now we've got a Linux/BSD
> > landscape out there with still pretty significant differences
> > between distributions and UNIX's progeny seem to be doing just
> > fine.
> > Were users looking for different things from their computers in
> > the 90s vs today? Have folks just gotten more used to variability
> > in computing environments and just accept it as part of the plan?
> Two things, I think:
> a) Today most identifiably Unix software is “sourceware”, and so the
> > differences between Linuxes, *BSD, and macOS are fairly easily
> > taken care of (eg. with autotools).
I'd also argue that (a) the differences between the Linuxes aren't as
big some people would make it out to be --- especially compared to the
differences between AIX and Solaris and HPUX, and (b) *BSD and macOS
has their ports and homebrew systems which also ease any pai that
isn't handled by autoconf and friends.
> b) A lot of Unix software is now distributed (more or less) by the
> OS vendor. Packaging has hidden the portability problem from the
> end user.
In addition to that, a lot of user-desired functionality is made
available via dynamic web "appliances" (e.g., GMail, Concur for those
people who need to submit travel reports) as opposed to compiled
binaries. I'm talking about pure web applications, of course, not
Java web apps.
My horror store from when I was working at IBM was that their expense
reporting tool was written in Java, but it only worked with the Sun
JRE. But if you needed to use to configure an IBM Bladeserver, that
only worked with the IBM JRE. So if I needed to submit an expense
report, I had to kill the browser, set the environment variables to
point at the Sun JRE, and then restart the browser and do the travel
report. And then when I needed to go back to messing with a Blade
Server chasis, I had to kill the browser, and reset the environment
variables, and then restart the browser.
Ah, Java.... write once, debug everywhere. :-)
next prev parent reply other threads:[~2022-11-10 6:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-09 22:01 [TUHS] " steve jenkin
2022-11-09 22:16 ` [TUHS] " Larry McVoy
2022-11-09 22:24 ` Clem Cole
2022-11-09 22:51 ` Joseph Holsten
2022-11-10 0:47 ` segaloco via TUHS
2022-11-10 0:54 ` Joseph Holsten
2022-11-10 1:28 ` David Arnold
2022-11-10 6:14 ` Theodore Ts'o [this message]
2022-11-10 9:12 ` David Arnold
2022-11-10 13:27 ` Tom Ivar Helbekkmo via TUHS
2022-11-10 15:33 ` Clem Cole
2022-11-10 1:42 ` Larry McVoy
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 \
* 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).