From: iking@killthewabbit.org (Ian King)
Subject: [TUHS] UNIX turns forty
Date: Fri, 5 Jun 2009 09:06:39 -0700 [thread overview]
Message-ID: <A9E1F085-A9BE-43B9-94F8-9D9784F8F429@killthewabbit.org> (raw)
In-Reply-To: <20090605144015.GA27542@mercury.ccil.org>
On Jun 5, 2009, at 7:40 AM, John Cowan wrote:
> Brian S Walden scripsit:
>
>> http://www.computerworld.com/action/article.do?
>> command=viewArticleBasic&articleId=9133570
>
> Not a bad article, really, but <rant>I do get very tired of this rigid
> separation of Linux and Unix. No, Linux doesn't have any AT&T code,
> but there isn't all that much left in Solaris or *BSD either (other
> than header files and such). And no, Linux distros aren't Unix-
> branded
> at present, but FWIU, that's because certification is neither fast nor
> cheap, and applies only to a given release. Commercial Linuxes
> have fast
> release cycles, and Debian, whose release cycles are slow, can't
> afford
> certification. But in terms of actual, rather than formal,
> compliance,
> Linux is as much a Unix as any branded Unix.</rant>
Not a very *good* article, either, IMHO. One gets the impression the
author of the piece was given two or three pieces of data and
instructed to write a historical drama around them. I also suspect
he's never seen a PDP-7, either. Until about two years ago, one of
these 'wimpy' machines was running a particle accelerator at the
University of Oregon. It was unnecessary to slam the PDP-7 to make
the point that Unix was created on a computer of modest resources.
Unix bloat occurred for the same reason any other piece of software
bloats up: users want to do less and get more. While it's true that
some programmers and companies are better than others at adding
features without adding heft, most find such exercise in economy
unnecessary given the "throw another giga[byte | hertz] at it"
culture that currently prevails.
It's also amusing he introduces the NT kernel as some sort of
'perfect foil' to Unix, without even mentioning its VMS roots - as
though it sprang fully formed from the aether. The reason NT was
competitive is that Unix configuration and administration has never
been a task for the meek. The goal of Windows was to reduce - or
hide - complexity and lower the intellectual 'cost' of entry. It's
not clear that newer versions have in fact accomplished that. :-)
In other words, this read like any other popularized account - which
would be expected, if it had been published in Ladies Home Journal.
-- Ian
next prev parent reply other threads:[~2009-06-05 16:06 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-05 3:48 Brian S Walden
2009-06-05 4:18 ` Larry McVoy
2009-06-05 11:42 ` Jim Capp
2009-06-05 14:40 ` John Cowan
2009-06-05 16:06 ` Ian King [this message]
2009-06-05 18:29 ` John Cowan
2009-06-06 5:20 ` Ian King
2009-06-05 18:40 ` Jason Stevens
2009-06-05 23:30 ` [TUHS] Wikipedia for Unix? Warren Toomey
2009-06-05 23:39 ` John Cowan
2009-06-06 0:17 ` Larry McVoy
2009-07-05 9:25 ` [TUHS] www.tuhs.org now a MediaWiki Warren Toomey
2009-07-05 17:28 ` Jim Capp
2009-06-05 23:50 ` [TUHS] Wikipedia for Unix? Al Kossow
2009-06-06 1:29 ` Jim Capp
2009-06-06 3:12 ` Greg 'groggy' Lehey
2009-06-06 4:11 ` John Cowan
-- strict thread matches above, loose matches on Subject: below --
2009-05-21 20:39 [TUHS] UNIX turns forty Brian S Walden
2009-05-19 4:42 Aharon Robbins
2009-05-19 6:13 ` Jason Stevens
2009-05-19 15:12 ` M. Warner Losh
2009-05-19 15:28 ` Michael Kerpan
2009-05-19 15:21 ` John Cowan
2009-05-15 16:48 Tim Newsham
2009-05-15 17:27 ` Jason Stevens
2009-05-15 18:09 ` Al Kossow
2009-05-19 2:20 ` Rafael R Obelheiro
2009-05-19 21:31 ` Warren Toomey
2009-05-19 21:49 ` John Cowan
2009-05-20 0:43 ` Jason Stevens
2009-05-20 4:56 ` Derek Peschel
2009-05-20 5:16 ` Jason Stevens
2009-05-20 8:21 ` Tim Bradshaw
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=A9E1F085-A9BE-43B9-94F8-9D9784F8F429@killthewabbit.org \
--to=iking@killthewabbit.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).