9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: jiho@smtp.popsite.net
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Are nvidia-cards working with plan9?
Date: Wed, 11 Oct 2000 08:47:55 +0000	[thread overview]
Message-ID: <39e37cf5@news2.starnetinc.com> (raw)
In-Reply-To: <20001005151052.3FEAB199DE@mail>

In article <20001009114925.A29182@cackle.proxima.alt.za>,
	lucio@proxima.alt.za (Lucio De Re) writes:

>> Actually, I wasn't laying blame, I was just alluding
>> to _de_facto_ reality.
>
> Well, Wall Street is just a special-interest group :-)

Yes, that certainly is a _de_facto_ reality.

>> There's a small matter of U.S. anti-trust law, and a
>> principle known as "fair access to essential
>> facilities".  It dates back to the railroad tycoons,
>> fer cryin' out loud.  Ironically, the case has been
>> made against Microsoft software.  It's even more
>> obvious with respect to chips, but as far as I know
>> (not very far) no one has tried making the case.
>
> The stated reason for not pursuing the case with the full might of
> the law was that _all_ IT companies had broken the law for years
> (software that ran only on some hardware, applications that ran
> only on given operating environment, etc) and the can of worms
> would have been far too big a problem...

Well, the stated reason is wrong.  There is a "reasonableness
clause" in the law, such that the remedy _cannot_ be unreasonably
onerous.

Requiring anyone who writes software to port and support on all
possible platforms would clearly be unreasonably onerous.

Chip companies, however, already have register-level documentation
for their own internal use, so making it public is not itself
onerous at all, especially with the Internet.  And support should
not be required, beyond keeping the documentation reasonably up
to date.

In other words, the circumstances are simply not comparable.  OS
writers shouldn't have to port to all hardware, and application
writers shouldn't have to port to all OSes.  However, OS companies
should have to provide reasonable documentation to all application
writers, and hardware complanies should have to provide reasonable
documentation to all OS writers.

> So we're lumped with legislation without teeth.  And the rest of
> the world is hardly likely to step into the US Government shoes
> and risk technological boycotts while they try to catch up :-(

It's not the legislation that lacks teeth.


--Jim Howard  <jiho@mail.c-zone.net>



  parent reply	other threads:[~2000-10-11  8:47 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-10-05 15:10 David Gordon Hogan
2000-10-09  9:05 ` jiho
2000-10-09  9:49   ` Lucio De Re
2000-10-11  8:47 ` jiho [this message]
  -- strict thread matches above, loose matches on Subject: below --
2000-10-05  0:29 okamoto
2000-10-04 13:07 Russ Cox
2000-10-04 13:21 ` Nigel Roles
2000-10-05  8:22 ` jiho
2000-10-05  9:00   ` Lucio De Re
2000-10-09  9:04     ` Douglas A. Gwyn
2000-10-09 10:02       ` Lucio De Re
2000-10-09 12:57         ` Rick Hohensee
2000-10-09 17:46         ` Matt
2000-09-25 10:57 forsyth
2000-09-25 13:38 ` Conor
2000-09-28 10:18   ` Douglas A. Gwyn
2000-10-02  9:01   ` root
2000-10-02 16:59     ` Scott Schwartz
2000-10-03  0:34       ` Rick Hohensee
2000-10-02  9:01   ` root
2000-10-03  8:49   ` Douglas A. Gwyn
2000-10-04  8:45   ` jiho
2000-10-04 11:55     ` sah
2000-10-04 12:06       ` sah
2000-10-04  9:08   ` jiho
2000-10-02  9:03 ` root
2000-09-21  8:58 nigel
2000-09-25  9:22 ` MoJoJoJo
2000-09-21  8:27 Henri Philipps

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=39e37cf5@news2.starnetinc.com \
    --to=jiho@smtp.popsite.net \
    --cc=9fans@cse.psu.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;
as well as URLs for NNTP newsgroup(s).