Microsoft Documentation Declared Unfit For US Consumption
anomalous cohort writes "Washington DC judge Colleen Kollar-Kotelly announced during the ongoing Microsoft antitrust hearings that their documentation is unfit for US consumption. This is relevant in an antitrust hearing as poor documentation on how to inter-operate with Microsoft's products is seen as an unfair barrier to entry for companies who compete with Microsoft. Others see this as yet another example of their crumbling hegemony or indolence as their empire burns."
"...Others see this as yet another example of their crumbling hegemony or indolence as their empire burns."
In this day and age of increasingly biased reporting, it is nice to see that Slashdot continues to present an objective, fair, and balanced approach to covering the issues.
Scuttlemonkey could work wonders for the Middle-East peace process!
For coders, at least. Documentation is for auditors.
And still others realize their documentation is probably no crappier than anyone else's.
There is a certain irony that the legal system decides someone else has poor documentation. The documentation of the law requires a graduate degree to use.
I'm no fan of Microsoft, but their documentation is ironclad compared to the law. Witness this case, it is only after the fact that it becomes vaguely clear that having poor documentation is wrong (even for a monopoly).
t
I've read lots of MS Documentation over the years -- white papers, APIs, and just general guidelines for things.
It's damned good documentation. It may not go to the border of 'special olympics' readers for Apple users, but for the majority of developers that are working on 'interoperability' the documentation is quite good. Not amazing, but the irony is still lost on me that a lawyer decided somebody else's documentation was bad.
Have you ever read the way bills are introduced into law? Jeez.
The price is always right if someone else is paying.
As the article says, Microsoft documents the things they want you to know very well (more software for Windows == good), so it's not like they have a corporate culture of crap documentation. What they don't do is document things they don't want you to know, like formats and protocols, because that would allow you to use non-Microsoft software somewhere (== bad).
Since their documentation is obviously biased, they're in trouble again.
Opportunity knocks. Karma hunts you down.