Open source conspiracy theorists warn that Microsoft's effort to make the code behind .Net, its software-development framework, open to the public to view — but not modify— is a trap. The goal? It's aimed, they claim, at tainting Mono, an open-source implementation of .Net, with the software maker's intellectual property. And why does this matter? Mono, you see, allows programmers to easily port software meant to run on Microsoft's Windows to Linux and other competing operating systems. But really, might Microsoft's critics be giving it too much credit for cleverness?
While Microsoft has been known to try just about every tactic in the book to undermine the competition, this paranoid theory mischaracterizes the open source community's beloved Mono. True, Mono, in theory, weakens Windows. But only in theory. In practice, Mono is not a threat to Microsoft — rather, it's spread the popularity of .Net far beyond Microsoft's Windows-developer base, and thereby tied the open-source developers who use it to Microsoft's software-development roadmap.
No, rather than a devious and elaborate ploy concocted in Microsoft's legal department, the right way to see Microsoft's Shared Source program is as a feeble attempt to mask its inability to move its business to the open-source model, as rivals IBM, Sun, Novell, Adobe, and Apple have done to varying extents. Sure, Microsoft could start suing developers — with the result, of course, that they'd simply drop .Net and move to other development tools untouched by Microsoft's hands. (Photo by BotheredByBees)











Comments
Storm, teacup.
Let's keep things in perspective here. All Microsoft are doing is making the source to the .NET libraries available to developers. Sun did this with Java from day one, a decade before anyone was even seriously suggesting an Open Source Java.
It's just a courtesy to developers. Sometimes if your code is doing something weird, it really helps to be able to step through the library source to see what's really going on under the hood.
As much as Microsoft deserves everything they get, it must really suck when even your most mundane decisions are microscopically analysed for the faintest signs of avarice or weakness.
I agree with everything carlfish wrote.
In addition, it's absurd to suggest that Mono represents "competition" to the genuine .NET product. It would, maybe, if the source for any end-user applications targetted at .NET were available (and could be relinked under Mono)... but they're not. Take, for example, VMware's Virtual Infrastructure 3: you can't use its real features (Virtual Center, VMotion, snapshot backups) unless you have a system running .NET. You *must* use .NET for that, because the executables are yours, but there's no binary that runs outside of Windows. You can't even run the VI3 client on anything that's not Windows. That's pretty much SOP for commercial software reliant upon .NET, so releasing the API (and implementation, which saves them support questions but costs them nothing) hurts MS in no way.
Start a discussion:
Login with your username and password below. Or comment on this post via email.
Forgot your username or password? New User?