Andy Updegrove has an interesting post up in which he analyzes a product comparison from InfoWorld's Randall Kennedy. The upshot of Kennedy's comparison of office productivity application suites is that he finds the commercially developed, non-open source SoftMaker suite of productivity applications to be the best suite for sharing and competing with Microsoft Office. He also fires off some notable criticisms of the open source OpenOffice suite. The funny thing is, SoftMaker is a small, commercial provider without an open source arm.
As is true of millions of people, I've used the OpenOffice productivity suite extensively, and I especially like the Go-oo fork of it. (Note that Go-oo has some backing from Novell, and by pass-through, from Microsoft.) That said, OpenOffice has been criticized for years for never quite achieving the level of document compatibility with Microsoft Office that it should have. I don't doubt that if OpenOffice had truly impressive compatibility with Office documents, it would have a much bigger user base than it has.
In analyzing this shortcoming a few months ago, Michael Meeks, a Novell employee, went so far as to pronounce OpenOffice "profoundly sick." We analyzed his thoughts here. He pointed to lack of growth in OpenOffice's development community in particular. In Kennedy's product comparison, he says this:
"OpenOffice.org 3.1 failed to deliver on its promise of better Microsoft Office interoperability. It severely mangled our Microsoft Word and Microsoft Excel test data files, and no amount of new features or targeted performance improvements could overcome this critical deficiency."
He's not the first person to note that SoftMaker's commercial suite is highly compatible with Microsoft Office documents. The suite sells for under $80 and is available for Windows and Linux. But, as Andy Updegrove notes, SoftMaker has only 17 employees, and doesn't leverage an open source development community, as OpenOffice does.
How can that be? As Updegrove notes:
"It seems bizarre that after all the ink and blood that's been spilled over the last several years over ODF and OOXML that OOo wouldn't deliver better interoperability, particularly if tiny SoftMaker was able to do a better job of it."
I have to agree, especially since OpenOffice is many years old and was started as a commercial suite. Perhaps it is time for a change in the way OpenOffice is developed. One thing to note here is that as Oracle acquires Sun Microsystems, it will also become the official steward of OpenOffice. Could Oracle make much needed changes, and finally help deliver a free, open source suite that competes effectively with Microsoft's? The first step in making such changes may be to look at what tiny little SoftMaker seems to be doing right.