From: "Ted Ts'o" <tytso@mit.edu>
To: Michael Witten <mfwitten@gmail.com>
Cc: Mike Galbraith <efault@gmx.de>, Richard Yao <ryao@ic.sunysb.edu>,
linux-kernel@vger.kernel.org
Subject: Re: UNIX Compatibility
Date: Wed, 25 May 2011 13:38:46 -0400 [thread overview]
Message-ID: <20110525173846.GG8476@thunk.org> (raw)
In-Reply-To: <c943132c8c364f95a91e3cf81cb0f2bd-mfwitten@gmail.com>
On Wed, May 25, 2011 at 03:17:35PM +0000, Michael Witten wrote:
>
> The winner is not the one who smashes the competition; the winner is the
> one who best eases the lives of as many people as possible.
>
> The point of such a specification is to provide a single, relatively stable
> source of documentation for how a complex system works.
I've been to ISO standards meetings, and it is filled with people who
use standards for the purposes of gaining a competitive advantage.
Most of them were paid to do standards work by companies who funded it
precisely because it would net them a competitive advantage.
I've represented the United States at official ISO meetings, and I saw
a lot more personality issues, corporate politics (i.e., a
representative from Sun who trying to torpedo ISO/IEC 23360-1:2006
because it would help Solaris and hurt Linux), than you would expect.
In fact, all of the technical work was done outside of the ISO
standards process; what we did inside ISO was all paper pushing,
because there were still so misguided government types in Europe who
cared about ISO at that time.
(As another example, I point you to the fireworks of OOXML and ISO/IEC
29500, and the blatent influcing of national standards bodies by
Microsoft.)
So if you want a specification of how **Linux** works, I don't think
going through ISO and national standards bodies is the most efficient
way to work.
>
> What needs to die is the tyranny of the hackers.
>
> Humans are capable of organizing themselves better than just acquiscing to
> whomever is capable of imposing himself fastest.
You know, biologists have a term for a static, stable system. It's
called "dead". If you want something that doesn't change, feel free
to use AT&T System V Release 4. It doesn't change. And it's well
documented.
Oh, you wanted the new features that's in Linux? The new hardware
support? That's all brought to you by the hackers that you seem to
hate so much.
- Ted
next prev parent reply other threads:[~2011-05-25 17:38 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-24 11:49 UNIX Compatibility Richard Yao
2011-05-24 13:06 ` Theodore Tso
2011-05-24 13:54 ` Michael Witten
2011-05-24 14:49 ` Richard Yao
2011-05-24 18:16 ` Ted Ts'o
2011-05-24 18:31 ` Michael Witten
2011-05-25 4:18 ` Mike Galbraith
2011-05-25 14:20 ` Michael Witten
2011-05-25 14:36 ` Ted Ts'o
2011-05-25 15:17 ` Michael Witten
2011-05-25 17:38 ` Ted Ts'o [this message]
2011-05-25 20:33 ` Casey Schaufler
2011-05-26 11:30 ` Bernd Petrovitsch
2011-05-26 11:30 ` Bernd Petrovitsch
2011-05-26 12:07 ` Valdis.Kletnieks
2011-05-26 12:24 ` Bernd Petrovitsch
2011-05-26 13:35 ` Ted Ts'o
2011-05-25 21:06 ` Valdis.Kletnieks
2011-05-25 14:38 ` Ted Ts'o
2011-05-25 15:17 ` Mike Galbraith
2011-05-25 15:21 ` Michael Witten
2011-05-24 18:23 ` david
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=20110525173846.GG8476@thunk.org \
--to=tytso@mit.edu \
--cc=efault@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mfwitten@gmail.com \
--cc=ryao@ic.sunysb.edu \
/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