Bugs In Microsoft Technical Documentation Rising 146
snydeq writes "The number of bugs in technical documentation for Microsoft communication protocols continues to grow, according to court documents filed for ongoing antitrust oversight of the company in the US. Problems with the technical documentation — which includes 1,660 identified bugs as of Dec. 31, up from 1,196 bugs on Nov. 30 — remain the major complaint from lawyers representing the group of 19 states that joined the US Department of Justice's antitrust lawsuit against Microsoft. Lawyers for the states have complained repeatedly that technical documentation issues are opening faster than Microsoft can close them. Nearly 800 Microsoft employees are working on the more than 20,000 pages of technical documentation, according to the court documents filed Wednesday."
Shocked, shocked that there is gambing going on... (Score:4, Interesting)
... ... ... ...
I think that MS needs to realize that one of the major reasons that standards exist is to PREVENT these things from happening. If there weren't so many inconsistencies, this would be markedly more difficult.
But what do I know about MS anyway? Who am I to comment on their ineptitudes? I use Linux.
Re:"Bugs"? (Score:1, Interesting)
They could start.. (Score:4, Interesting)
They should prioritize, but I'll do it for them.
1.)SMB
2.)TDS
3.)whatever the hell goes on with Exchange
4.)remote desktop
5.)MSN
6.)the rest
Re:To the editors (Score:3, Interesting)
And then telling other people to stop whining and just install a shitblocker.
Yes I know ads aren't that bad (normally anyway).
Re:To the editors (Score:3, Interesting)
Print view [infoworld.com]
I would contend that all articles should link to the print preview if the article has obnoxious ads or superfluous page breaks, but then they'd just stop providing print views.
Keep this to yourselves. ;)
Re:I'm sympathetic (Score:4, Interesting)
Because it causes problems for THEM, regardless of the EU.
This may be apocryphal, but ISTR reading somewhere that when they needed documentation (for internal purposes) on SMB, they had to use the Samba guys' stuff.
Re:I'm sympathetic (Score:3, Interesting)
It may be awesome, but it's symptomatic of a poor development culture at MS, and ties back into the lack of protocol documentation.
Re:At least there is documentation! (Score:3, Interesting)
Re:To the editors (Score:1, Interesting)