Microsoft FUD Machine Aims at OpenOffice.org
Roblimo writes "If you're using Microsoft Office and considering a switch to (free) OpenOffice.org, Microsoft would like you to read their Open Office Competitive Guide first, in which they tell you how much better/faster/cheaper MS Office is than OOo. Taran Rampepersad, an IT consultant in Trinidad, believes this "Competitive Guide" is nothing but FUD, so he wrote a detailed rebuttal to it -- and released his article under the FDL so you can feel free to republish his piece or share it with anyone you like, however you like." A followup to this story. Newsforge and Slashdot are both part of OSDN.
and my MS Office-using (on a Mac even) advisor is sixpence none the wiser. Total FUD.
Comparing it to Windows will be a moot point, since El Dorado is going to have a 40% larger code base than XP.
I'm no fan of MS (I'm browsing from FireFox within Linux), but he gives short shrift to the problem of macro/VBA conversion. The fact of the matter is that the documentation on the OO API absolutely stinks, and any business with a substantial investment in its current automation would have to think not once, not twice, but long and hard about the costs of conversion.
Reading some of the more key points with OO it reminded me of some of the reasons that I am such a big fan of OSS and the OS movement. With these open (or at least more open than MS and the like) standards it gives a good feeling that you are in control of your data and the documents, etc. you create. When I would use a tool such as MS Office I would feel that I'm making the document for it or as a kind of expansion of it rather than as a self-created work for me. This sent a tinge of concern through me for quite some time. I know it is probably silly for me to feel a sense of liberation and it's really not anything I can describe properly. I guess I just enjoy the freedom permissible by using a standard that is not owned and controlled by an entity that has little to no desire for openness. With quality suites like OO I feel that once users get this feeling that they are in control of their own works - or at least more-so then they were - they will make the migration which will only bring futher support to the OSS community.
( o ) one could say I'm rather baked
Where I am working, I have a Suse Linux desktop, and can use a Microsoft Terminal Server should I need it. I could have had a Microsoft Windows desktop, if I chose so. People at work can use Microsoft Office or OOo.
I am aggressively using OOo file formats in my daily communication. That is, all documents that I am sending are being sent out as sx? files, and if I am receiving MS office documents, I convert them to OOo anyway in order to work with them, and send them back in sx? formats. Usually, I include a customary copy of a PDF export with the document.
This strategy works nicely. Almost all the people I work with now have OOo included in their installation. In fact, new machines in my workplace will soon include OOo as a standard installation, I hope. Some people are starting to send documents in sx? formats as I do.
External communication is the next target. I will force our suppliers and partners to learn what OOo is and how to use it as well.
This is how you establish a standard: Document it (OOo file formats are nicely documented) and then use brute force to publicize it.