In somewhat of a surprising and considerably bold move, Microsoft has recently announced a new strategy that will place them in a friendlier position in terms of open interoperability. In short, they will be publishing their application programming interfaces (APIs) and communication protocols for their high volume products. These products include Windows Vista, the .NET Framework, Windows Server 2008, SQL Server 2008, Office 2007, Exchange Server 2007, and Office SharePoint Server 2007. Microsoft has also pledged not to sue open-source developers who create noncommercial software based on Microsoft's protocols. With that said, let's take a look at what exactly this means for Microsoft, Open Source, and us, the consumers.
To clarify, Microsoft is opening up their APIs, not their source codes. This means that Open Source developers do not have access to how the programs work, but more so how the applications interact with one another. Examples of what we can see as a result, include Mozilla's Thunderbird communicating more tightly with Microsoft's Exchange Server, and possibly replacing Microsoft Outlook as our mandatory mail client. As Paul Thurrott pointed out on the Windows Weekly podcast, we may now be able to sync Google Calendar appointments to our mobile phones without having to jump through chutes and ladders. Perhaps we can get some Macro support in Open Office?
The reason that this announcement is such a surprising move, is because Microsoft has never made life easy for open source developers. Though there exists industry standards that Microsoft are expected to abide by, Microsoft has a habit of forcing their own standards on consumers. Case in point, is the Open Document Format (.odf) that is standardized throughout non-Microsoft office suites, such as Open Office and Lotus Symphony. Microsoft has never embraced the format, while strongly advocating usage of their proprietary OOXML (.xml) format. Being the near monopoly that Microsoft is, they have the clout to set the standards themselves, while bullying any company that attempts to infringe upon their trademarks. These practices have often gotten Microsoft in hot water with committees such as the European Union, whom has sued Microsoft for abuse of their dominant position in the market.
Though it may seem like Microsoft is seeing the light and evolving with the times, some Open Source programmers remain skeptical. For one, Microsoft's pledge to not sue Open Source companies, only applies to non-commercial usage. Thus Microsoft will only play nice, so long as those companies don't plan on profiting off of the agreement. This may be seen as a blatant method of Microsoft maintaining their foothold on the industry. Some individuals believe that Microsoft is only taking these steps to get the European Union off their back, and are also attempting to ensure that their own formats are standardized. Basically, Microsoft is allowing others to adopt their formats, but not committing to embrace those that are already accepted as standards by the Open Source community. Though it seems as it is Open Source, and the consumers as a whole, that are benefiting from this agreement, it is clearly Microsoft that is the true winner.
To clarify, Microsoft is opening up their APIs, not their source codes. This means that Open Source developers do not have access to how the programs work, but more so how the applications interact with one another. Examples of what we can see as a result, include Mozilla's Thunderbird communicating more tightly with Microsoft's Exchange Server, and possibly replacing Microsoft Outlook as our mandatory mail client. As Paul Thurrott pointed out on the Windows Weekly podcast, we may now be able to sync Google Calendar appointments to our mobile phones without having to jump through chutes and ladders. Perhaps we can get some Macro support in Open Office?
The reason that this announcement is such a surprising move, is because Microsoft has never made life easy for open source developers. Though there exists industry standards that Microsoft are expected to abide by, Microsoft has a habit of forcing their own standards on consumers. Case in point, is the Open Document Format (.odf) that is standardized throughout non-Microsoft office suites, such as Open Office and Lotus Symphony. Microsoft has never embraced the format, while strongly advocating usage of their proprietary OOXML (.xml) format. Being the near monopoly that Microsoft is, they have the clout to set the standards themselves, while bullying any company that attempts to infringe upon their trademarks. These practices have often gotten Microsoft in hot water with committees such as the European Union, whom has sued Microsoft for abuse of their dominant position in the market.
Though it may seem like Microsoft is seeing the light and evolving with the times, some Open Source programmers remain skeptical. For one, Microsoft's pledge to not sue Open Source companies, only applies to non-commercial usage. Thus Microsoft will only play nice, so long as those companies don't plan on profiting off of the agreement. This may be seen as a blatant method of Microsoft maintaining their foothold on the industry. Some individuals believe that Microsoft is only taking these steps to get the European Union off their back, and are also attempting to ensure that their own formats are standardized. Basically, Microsoft is allowing others to adopt their formats, but not committing to embrace those that are already accepted as standards by the Open Source community. Though it seems as it is Open Source, and the consumers as a whole, that are benefiting from this agreement, it is clearly Microsoft that is the true winner.
0 comments:
Post a Comment