The better Office alternative: SoftMaker Office bests OpenOffice.org ( - Softw... - The Diigo Meta page

• 30 Jun 09
  

  Gary Edwards

  Article discussing the importance of office suite alternatives having a high level of comaptibility with MSOffice, the MSOffice binary formats, and the MSOffice productivity environment. ComputerWorld's Randall Kennedy has done exhaustive work comparing the conversion quality of MSOffice documents from two alternative office suites: Softmaker Office and OpenOffice.

  OpenOffice Softmaker-Office MSOffice compatibility interoperability

  • Frankly, from Microsoft's perspective, the danger may have been overstated. Though the free open source crowd talks a good fight, the truth is that they keep missing the real target. Instead of investing in new features that nobody will use, the team behind OpenOffice should take a page from the SoftMaker playbook and focus on interoperability first. Until OpenOffice works out its import/export filter issues, it'll never be taken seriously as a Microsoft alternative.

    
    

    More troubling (for Microsoft) is the challenge from the SoftMaker camp. These folks have gotten the file-format compatibility issue licked, and this gives them the freedom to focus on building out their product's already respectable feature set. I wouldn't be surprised if SoftMaker got gobbled up by a major enterprise player in the near, thus creating a viable third way for IT shops seeking to kick the Redmond habit.

    • 

      Gary Edwards on 2009-06-30

      This quote is an excerpt from the article :)
• 

  Kelley Vendeland

  Competitive review

Public Stiky Notes

• 
  Gary Edwards on 2009-06-30
  This quote is an excerpt from the article :)

Page Comments

• 
  Gary Edwards on 2009-06-30
  Finally! Someone who gets it. For an office suite to be considered as an alternative to MSOffice, it must be designed with multiple levels of compatibility. It's not just that the "feature sets" that must be comparable. The guts of the suite must be compatible at both the file format level, and the environment level.
  
  Randall put's it this way; "It's the ecosystem stupid".
  
  The reason ODF failed in Massachusetts is that neither OpenOffice nor OpenOffice ODF are designed to be compatible with legacy and existing MSOffice applications, binary formats, and, the MSOffice productivity environment. Instead, OOo and OOo-ODF are designed to be competitively comparable.
  
  As an alternative to MSOffice, OpenOffice and OpenOffice ODF cannot fit into existing MSOffice workgroups and producitivity environments. Because it s was not designed to be compatible, OOo demands that the environment be replaced, rebuilt and re-engineered. Making OOo and OOo-ODF costly and disruptive to critical day-to-day business processes.
  
  The lesson of Massachusetts is simple; compatibility matters. Conversion of workgroup/workflow documents from the MSOffice productivity environment to OpenOffice ODF will break those documents at two levels: fidelity and embedded "ecosystem" logic.
  
  Fidelity is what most end-users point to since that's the aspect of the document conversion they can see. However, it's what they can't see that is the show stopper. The hidden side of workgroup/workflow documents is embedded logic that includes scripts, macros, formulas, OLE, data bindings, security settings, application specific settings, and productivity environment settings. Breaks these aspects of the document, and you stop important business processes bound to the MSOffice productivity environment.
  
  There is no such thing as an OpenOffice productivity environment designed to be a compatible alternative to the MSOffice productivity environment.
  
  Another lesson from Massachusetts is that "rip-out-and-replace" is both costly and disruptive. If it can be done. Amazingly, the City of Munich has been working on the rip and replace of MSOffice for over six years, and they are reporting that the project is only 60% complete.
  
  There are alternatives to rip and replace. The Massachusetts choice was to re-purpose MSOffice using an ODF plug-in approach - a clone of the Microsoft Compatibiltiy Pack if you will.
  
  Another alternative is to design from the ground up, a highly compatible office suite that can slide into these MSOffice bound environments without show stopping disruption. Softmaker Office is not alone in this approach, with Evermore Office and ThinkFree Office also proving that a very high level of compatiblitiy with MSOffice, the MSOffice binary formats, and the MSOffice productivity environment, is possible.
  
  Excerpt: "In the kingdom of business productivity, Microsoft Office reigns supreme. Its dominating position atop the word processing, spreadsheet, and presentations heap seems virtually unassailable. Its file formats define an industry, and its component applications are often synonymous with the underlying tasks they perform. ......"
  
  "There's no doubt about it: Office's roots run deep -- deeper, even, than its host OS, Microsoft Windows. People talk about switching Windows versions all the time. However, few souls are willing to walk away from their current version of Office for fear of losing interoperability with their peers, a fact that makes dislodging this sprawling, well-entrenched entity all the more daunting -- though many alternative productivity suites and SaaS offerings continue to try......"

Would you like to comment?

Join Diigo for a free account, or sign in if you are already a member.