Three Things Microsoft Should Do --V.2
In the last year or so, Microsoft has earned the ire of partners, governments and customers. Forgetting about the Vista blunders, I think that one of Microsoft biggest mistake is to try to induce FUD (Fear Uncertainty & Doubt) into the FLOSS (Free/Libre/Open Source Software) movement.
In a way, I can't blame Microsoft for that. After all, Linux is on the rise, the cost of machines is on the drop and customers continue to look for ways to save money and free themselves from Microsoft's illegal monopoly.
What irks me is that Microsoft seems to think I'm stupid and I'm just going to swallow whatever FUD they send my way. I'd like to think that I'm far from being the only user who is annoyed at how Microsoft is treating us. We are not sheep that exists only to pay a tax to Microsoft (which I don't).
If Microsoft is serious about working with the open source community, here are three things I need to see before I consider working with Microsoft.
Support ODF in Microsoft Office
Sure, they can keep using their half-baked OOXML, but there is not a single valid technical reason why Microsoft Office does not support ODF. Microsoft does not want documents to be interchangeable from office suite to office suite. In other words, OOXML and it's attempt at ISO certification is there only so that Microsoft continues to entrench governments with Microsoft Office.
Use the GNU GPL 3
Most free software is released under the GNU GPL 2 or 3, which is incompatible with Microsoft's OSP (Open Specification Promise) and the Ms-PL (Microsoft Public License). This is not an accident. Microsoft does not want software written using their technology to spread to other platform. Again, it's vendor lock-in. If Microsoft truly wanted to work with the Open Source community, they should abandon the OSP and the Ms-PL for the GPL, or another OSI certified license.
Use and Contribute to Existing Standards
I know this is very similar to the above to challenges, but Microsoft has a fascination with re-writing code that already exists. For example, NUnit provides everything that a developer needs to do unit testing, but Microsoft re-created the same functionality in Visual Studio Team Edition. Using Windows Metafiles and DrawingML instead of the W3C SVG (Scalable Vector Graphics) recommendation. Creating the WMA file format when MP3 or Ogg already exists. Let's not get into Java vs. .NET!
This fascination with re-creating the wheel means that the world is always split between true standards (ISO, W3C, etc), and Microsoft. More standards is not better for the customer. If that was the case, there would be different type of incompatible CDs, DVDs and even television that work only for a single cable providers. By having a single standard for CDs, it means that I can buy a CD from Sony (minus the rootkit), and play it in a Panasonic player without having to worry about incompatibilities.
Until I see more action from Microsoft on those three fronts, I will happily continue to develop application on my Linux machine, and I will not care if they work on Microsoft platforms or not.
In the last year or so, Microsoft has earned the ire of partners, governments and customers. Forgetting about the Vista blunders, I think that one of Microsoft biggest mistake is to try to induce FUD (Fear Uncertainty & Doubt) into the FLOSS (Free/Libre/Open Source Software) movement.
In a way, I can't blame Microsoft for that. After all, Linux is on the rise, the cost of machines is on the drop and customers continue to look for ways to save money and free themselves from Microsoft's illegal monopoly.
What irks me is that Microsoft seems to think I'm stupid and I'm just going to swallow whatever FUD they send my way. I'd like to think that I'm far from being the only user who is annoyed at how Microsoft is treating us. We are not sheep that exists only to pay a tax to Microsoft (which I don't).
If Microsoft is serious about working with the open source community, here are three things I need to see before I consider working with Microsoft.
Support ODF in Microsoft Office
Sure, they can keep using their half-baked OOXML, but there is not a single valid technical reason why Microsoft Office does not support ODF. Microsoft does not want documents to be interchangeable from office suite to office suite. In other words, OOXML and it's attempt at ISO certification is there only so that Microsoft continues to entrench governments with Microsoft Office.
Use the GNU GPL 3
Most free software is released under the GNU GPL 2 or 3, which is incompatible with Microsoft's OSP (Open Specification Promise) and the Ms-PL (Microsoft Public License). This is not an accident. Microsoft does not want software written using their technology to spread to other platform. Again, it's vendor lock-in. If Microsoft truly wanted to work with the Open Source community, they should abandon the OSP and the Ms-PL for the GPL, or another OSI certified license.
Use and Contribute to Existing Standards
I know this is very similar to the above to challenges, but Microsoft has a fascination with re-writing code that already exists. For example, NUnit provides everything that a developer needs to do unit testing, but Microsoft re-created the same functionality in Visual Studio Team Edition. Using Windows Metafiles and DrawingML instead of the W3C SVG (Scalable Vector Graphics) recommendation. Creating the WMA file format when MP3 or Ogg already exists. Let's not get into Java vs. .NET!
This fascination with re-creating the wheel means that the world is always split between true standards (ISO, W3C, etc), and Microsoft. More standards is not better for the customer. If that was the case, there would be different type of incompatible CDs, DVDs and even television that work only for a single cable providers. By having a single standard for CDs, it means that I can buy a CD from Sony (minus the rootkit), and play it in a Panasonic player without having to worry about incompatibilities.
Until I see more action from Microsoft on those three fronts, I will happily continue to develop application on my Linux machine, and I will not care if they work on Microsoft platforms or not.
Last edited:
