News

The Microsoft Consent Decree Expires

On May 12, the consent decree produced by the case of United States vs. Microsoft formally expired. The legal judgment in that case was rendered in 2002 over antitrust concerns.

The original case was filed on May 18, 1998 and was settled on Nov. 12, 2002 with a federal court's final judgment. Microsoft was named by the court as a "monopolist" because of its control over the operating system market with Windows.

The DoJ's announcement implied that an extension of the final judgment's terms, which concerned the oversight of Microsoft's documentation, has ended too.

"Certain provisions in the Microsoft final judgment expired in November 2007," the DoJ explains at the end of its announcement. "Other provisions relating to Microsoft's obligation to make certain interoperability information available to third parties have twice been extended with Microsoft's consent. As these issues have now been resolved, it is appropriate for the final judgment to expire."

The DoJ appears to be referring to extensions that Microsoft agreed to concerning its documentation process. Microsoft voluntarily agreed to ensure, with DoJ oversight, that its published software documentation and APIs will enable interoperability with other software products. That effort was headed by former President of the Server and Tools Business, Bob Muglia, who stepped down in January. Muglia was replaced by Satya Nadella in February. Microsoft initiated a broad program in 2008 to open up its APIs and documentation, which may have been instigated, in part, due to antitrust litigation, both in the United States and abroad.

Microsoft has faced parallel anti-competition legal charges in the European Union, specifically over Windows Server interoperability issues, as well as the distribution of its Windows Media Player and Internet Explorer browser via Windows. In the latter case, the European Commission held Microsoft to stricter standards than in the United States. Microsoft was required to give users a choice of competing browsers by issuing a browser ballot to Windows users. An idea that Microsoft would be compelled to sell Windows in Europe without Internet Explorer was scrapped, however.

In the U.S. courts, Microsoft had argued that Internet Explorer could not be separated from Windows as a distinct program. Microsoft's CEO Steve Ballmer has described Internet Explorer as "a feature" of Windows in recent years. To this day, Microsoft's software lifecycle ties its browser with Windows, even though both pieces of software are routinely released separately and at different times.

Internet Explorer Wins

Most people associate the case with complaints by Netscape Communications Corp. that its Navigator Web browser was excluded from fair U.S. market competition. Microsoft was accused of using its control of the Windows operating system markets to game the browser market, giving unfair advantage to its Internet Explorer browser.

Even though Netscape "won" the legal battle in the 1998 case, it ultimately lost the big browser war. In the mid-1990s, Netscape Navigator held more than 90 percent of the browser market, but by the end of 2006, that market share had plummeted to less than one percent, according to one estimate. Had U.S. legal authorities required Microsoft to initiate a browser ballot, the story for Netscape might have been different.

Internet Explorer currently dominates the browser market with 55 percent use, according to Net Applications' data, with the next runner up being Firefox at 22 percent. The nonprofit Mozilla Foundation built Firefox as an open source project, mostly based on code remaining from the ashes of Netscape's earlier efforts.

Microsoft had little to say about the expiration of this final judgment, except to indicate that its practices have changed.

"Our experience has changed us and shaped how we view our responsibility to the industry," a Microsoft spokesperson stated via e-mail. "We are pleased to bring this matter to successful resolution, and we are excited to keep delivering great products and services for our partners and customers."

For its part, the DoJ viewed the case as a victory for consumers and competition, stating that "the judgment protected the development and distribution of middleware -- including web browsers, media players and instant messaging software -- thereby increasing choices available to consumers."

Some issues may still live on concerning Microsoft's past competition practices. An appeals court this month cleared the way for Novell (newly acquired by Attachmate Corp.) to sue Microsoft over antitrust claims associated with WordPerfect, which Novell owned in 1994. Novell's complaints are associated with the use of the operating system market control to exclude applications, as well as allegations that exclusionary agreements were in place with original equipment manufacturers, hurting WordPerfect distribution and helping Microsoft Word.

About the Author

Kurt Mackie is senior news producer for 1105 Media's Converge360 group.

comments powered by Disqus

Featured

  • Compare New GitHub Copilot Free Plan for Visual Studio/VS Code to Paid Plans

    The free plan restricts the number of completions, chat requests and access to AI models, being suitable for occasional users and small projects.

  • Diving Deep into .NET MAUI

    Ever since someone figured out that fiddling bits results in source code, developers have sought one codebase for all types of apps on all platforms, with Microsoft's latest attempt to further that effort being .NET MAUI.

  • Copilot AI Boosts Abound in New VS Code v1.96

    Microsoft improved on its new "Copilot Edit" functionality in the latest release of Visual Studio Code, v1.96, its open-source based code editor that has become the most popular in the world according to many surveys.

  • AdaBoost Regression Using C#

    Dr. James McCaffrey from Microsoft Research presents a complete end-to-end demonstration of the AdaBoost.R2 algorithm for regression problems (where the goal is to predict a single numeric value). The implementation follows the original source research paper closely, so you can use it as a guide for customization for specific scenarios.

  • Versioning and Documenting ASP.NET Core Services

    Building an API with ASP.NET Core is only half the job. If your API is going to live more than one release cycle, you're going to need to version it. If you have other people building clients for it, you're going to need to document it.

Subscribe on YouTube