Advanced

Why Microsoft Suddenly Wanted to Be More Interoperable - Comes v. MS Exh. 7068 Tells Us

Posted by Scott_Ruecker on · 4 comments
Groklaw
Mail this story
Print this story

Guess why Microsoft suddenly decided it wanted to be more interoperable? It's so it can get customers to quit using Linux and switch to Windows & .NET. Remember when Microsoft told us it was interested in greater interoperability with Linux because their customers were demanding it? That part is true, as I'll show you. But the purpose of developing greater interoperability at the request of Intel, according to this exhibit, was so that Microsoft could get Intel to switch its development environment from Linux to Windows. Intel's Paul Otellini had reportedly asked his people to figure out how to do that.

["..and at Intel, the developer crowd was raised on Unix/Linux. They just don’t WANT to move."..I Love It! - Scott]

Full Story

  Nav
» Read more about: Story Type: News Story; Groups: Intel, Linux, Microsoft

» Get new stories by e-mail: nightly or as they are published

« Return to the newswire homepage

  Related stories
» More like this

Comments (4)

Every API, every protocol, everything in the entire Linux environment is well documented.

If Microsoft wanted to actually be interoperable, they could be so easily.

Any asking for help that they do is because they want to pretend, to obfuscate, to LIE.

Microsoft, as a company, has never and will never do anything that they do not first believe is in the best interest of Microsoft, which means they do nothing that isn't designed from inception to extend their desktop dominance.

I recall when they paid their "monopoly" prosecution fines by "donating" Windows licenses, writing them off their fine at the RETAIL PRICE, to schools. What better way to not only erase their "debt to society", but to lock in lots of taxpayers to the upgrade treadmill while inculcating more and more students with the Windows Way Of Life.
@Bob_Robertson You've hit the nail on the head...

Interoperability when implemented by Microsoft only goes one way... to their platforms, and once there, locks in as much as possible. Any two way interoperability is always implemented by the outside (FOSS or other commercial vendor) and Microsoft tends to go out of their way to break that as quickly and painfully as possible.
Quoting:Interoperability when implemented by Microsoft only goes one way... to their platforms, and once there, locks in as much as possible. Any two way interoperability is always implemented by the outside (FOSS or other commercial vendor) and Microsoft tends to go out of their way to break that as quickly and painfully as possible.
And not even three weeks ago, Andy Updegrove gave a "somewhat-mixed, factfinding" review of the CodePlex Foundation; the most recent of the touted joint FOSS/MS ventures. See Updegrove's 'CodePlex Foundation Reports on 100 Day Goals' found at http://www.consortiuminfo.org/standardsblog/article.php?stor...

CodePlex Foundation proceedings could indeed turn out to provide a timely study of this relatively new entity in Microsoft's "Interoperability" arsenal, along with a sampling of the actual methods used to achieve its ultimate goals through such "Interoperability" ventures.

Post a comment

A free account is needed to post. Write your comment here first: your text is kept in this browser while you sign up or log in, and is waiting for you when you come back.

Your message:
|||||
10
Markdown: **bold**, *italic*, [text](https://link), - lists, > quotes, $x^2$ for math. Formatting help

Sign up and post (it is free)  or  Log in and post