From the Editors: Microsoft and open source
By SD Times News Team
January 15, 2009 —
(Page 1 of 2)
Microsoft has long had a hate-hate relationship with open source—not only with specific open-source projects like Linux, but also with the concept of non-proprietary software.
It’s not hard to see why Microsoft execs like Bill Gates and Steve Ballmer have been historically vitriolic about open source. Many of Microsoft’s most profitable products have open-source competitors. To name just a few: Windows has Linux. IIS has Apache. SQL Server has MySQL. Visual Studio has Eclipse and NetBeans. Internet Explorer has Firefox. Office has OpenOffice. .NET has Java (which is sort of open source).
Some of those competitors, like Linux-based servers, represent a serious long-term threat to Microsoft’s revenue. Others, like OpenOffice, haven’t had a significant impact. Even so, Microsoft has also had a philosophical difference with the entire open-source movement. Ballmer, for example, has made public statements claiming that open-source software is a cancer and that open-source software is not trustworthy.
One should not blame Microsoft for speaking out against competing products and against a model for software development that’s the opposite of its own closed-source, proprietary-protocols model for customer lock-in. As a for-profit company, Microsoft’s executives have a fiduciary responsibility to consider their company’s revenues. If they honestly believe that open source is a threat to their revenue, they have no choice but to fight against it.
However, it’s clear that today Microsoft does not see open source as a complete threat like it did in the early 2000s, when it was most vocal against Linux and other open-source projects. As our interview with Sam Ramji shows, Microsoft is beginning to provide its product teams with the flexibility to work with open-source software and to consider interoperability with open-source software.
That last point is the key. SD Times doesn’t care if Microsoft ever releases any of its software as open source. There’s nothing wrong with Microsoft’s closed-source business model, as its continuing profits, and popularity, with consumers and enterprise customers show.
What we do care about is interoperability. Microsoft has made some strides in recent years to publish its APIs, file formats and communications protocols. In many or most cases, the impetus behind that release has been compliance with a court order or to head off a challenge requiring interoperability. In each case, it seems like Microsoft has to be dragged, kicking and screaming, into releasing the documentation or in pledging not to sue developers who build independent implementations of its protocols.
Related Search Term(s): open source, Microsoft
Share this link: http://sdt.bz/33188
Most Read Latest News Blog Resources
Android is the focus of two new design tools
Anywhere Software and Xamarin provide ways for developers to create and test their applications on PCs
|
|
LEADTOOLS HTML5 add-on modules released
Including New HTML5 Zero Footprint Viewer, JavaScript Libraries and RESTful Web Services for Document and Medical SDKs
|
|
How to speed up your Cukes
Using a five-step process derived from Six Sigma, Cucumber tests can go much faster
|
|
WhiteSource offers open-source license management as a service
Software gives companies insight into the open-source components in products
|
SmartBear rolls out new quality solution: API Complete
Software gives organizations ability to write test scripts and monitor APIs by bridging the DevOps divide
|
|
Android is the focus of two new design tools
Anywhere Software and Xamarin provide ways for developers to create and test their applications on PCs
|
|
WhiteSource offers open-source license management as a service
Software gives companies insight into the open-source components in products
|
|
Top five devices you can integrate with your applications
A five-fingered list of common, household items with which you can talk to (via software, of course)
|
Slick...but who needs it?
compilr.com is a well-designed site and the folks behind it seem to have their heart in the right place. But...who needs it?
|
|
How to be a better software developer
Want to be a better developer? You won't get there by mastering an interesting language or learning a new set of APIs.
|
|
Wooing Galatea
Do yourself a favor and check out Galatea 2.2, a wonderful book by novelist Richard Powers.
|
|
The world as story
An artificial-intelligence system at Carnegie Mellon seeks to understand the world by making statements about it.
|
Five SCM Best Practices
Two-thirds of all software projects fail, according to the Standish Group’s CHAOS study. Improper usage of software configuration management...
|
|
|
Best Practices for Branching and Merging Patterns
Development teams often create a branching pattern, usually drawn out on a white board or in a Visio document, that is used as a model to...
|
|
Automated Error Reporting
We invite you to read a short e-zine that tells you all about automated error reporting for .NET applications. This 8-page e-zine is packed...
|
|
The End of Application Redeploys
Imagine that every time you wanted to write, send or receive an email, you needed to restart your computer. How much time would this take, a...
|