MozillaZine

Full Article Attached Microsoft Violated Sherman Antitrust Act

Monday April 3rd, 2000

In his ruling today, Judge Thomas Penfield Jackson found Microsoft in violation of the Sherman Antritrust Act, stating that "The Court concludes that Microsoft maintained its monopoly power by anticompetitive means and attempted to monopolize the Web browser market".

Microsoft's problem was that they had lost all credibility with the judge, and thus he had no option but to side with the facts presented by the government.

Click here to read an excerpt at ABCNews.com.

Here's a link to the ruling. Click "Full Article" below for some of our own excerpts. More to come, as we go over the ruling in more detail.


#41 Re: Re: That's because there IS NO DOM3...

by FrodoB

Tuesday April 4th, 2000 9:13 AM

You are replying to this message

There's a distinct difference here that you seem to overlook....

IE 5, if your argument is to hold water, must conform to standards that have been previously written. No one expects Netscape 4.0 to conform to specs that were finished after it was written (4.72 is another story, but we have Mozilla to count on for that). Likewise, IE 4 shouldn't be expected to conform to unfinished DOM specs. But by the time IE 5 was released, the DOM 1 specs had been out for a year or more. If your argument is to hold water, IE 5 MUST comply with older specifications. Certainly, browsers written before the release of the specs can't be expected to be compliant. But browsers written YEARS after the specs are released cannot be expected NOT to conform with the specs (yes, I know, it's a double negative; it's there for emphasis). I would throw the blame equally at Netscape for this, but they decided to go with Mozilla and aim for compliance in the future instead of adding it on top of an architecture that couldn't handle it in the present (we're talking late 1998, not early 2000 in this context). If MS decides to do the same (make a new rendering engine that actually complies to the W3C specs [even Tasman doesn't, and it was hyped for exactly that reason!]), then I have no problem here. Hell, it would solve a bunch of browser compatibility problems (if we could write to the specs and have them guaranteed to work on 95% of desktops, life is good).