Slashdot Mirror

The list of highly questionable if not outright illegal activities is very long:

You can start here with "A History of Anticompetitive Behavior and Consumer Harm"
http://www.ecis.eu/documents/Finalversion_Consumerchoicepaper.pdf

and then move on to a catalog of their attacks on standards:
http://www.grokdoc.net/index.php/Dirty_Tricks_history

and then any of these:
Illegal tying: http://www.ecis.eu/documents/ECISPressStatementonOperaSO1.pdf
Unethical marketing: http://www.nearsoft.com/blog/MS-test.html
Antitrust: http://news.bbc.co.uk/2/hi/business/600488.stm

Or these:
http://slashdot.org/story/00/05/02/158204/Kerberos-PACs-And-Microsofts-Dirty-Tricks
http://www.technologyevangelist.com/2007/02/microsoft_dirty_tric_1.html
http://techrights.org/2008/12/01/leaked-oem-vista-ad-incentives/
http://lxer.com/module/newswire/view/57261/index.html
http://news.bbc.co.uk/2/hi/business/368660.stm
http://www.groklaw.net/staticpages/index.php?page=2005010107100653
http://yro.slashdot.org/story/06/08/23/1251210/Microsoft-Admonished-by-US-District-Court-Judge
http://www.zdnet.com/blog/microsoft/microsoft-tried-to-muck-with-anti-linux-facts/235
http://www.zdnet.com/news/fact-and-fiction-in-the-microsoft-sco-relationship/139743
http://www.kuro5hin.org/story/2001/10/23/13219/110
http://lproven.livejournal.com/102128.html
http://www.linuxjournal.com/article/7654

The thing is, you have to have trust in version control to be prepared to use it. You are putting your business in its hands, so it had better not break or introduce errors on purpose. Trust depends upon your reputation. Reputation matters.

Would you put your trust in the safety of your product in the hands of a company to whom the continued life of your product represented part of a competitive threat to their platform?

We also have learned that Microsoft may even be above the law in some respects.

We also have learned that Microsoft may even be above the law in some respects.

Cringely posted the story in two parts, but the summary only links to the first. Second part here.

Microsoft dirty tricks, part two