Java and OpenOffice.org 2.0
Tuesday, March 29th, 2005Like many FOSS advocates, I have tried to encourage the uptake of FOSS software by suggesting users switch to free, better alternatives on an application by application basis: don’t use Internet Explorer, use Firefox instead; use Thunderbird instead of Outlook or Outlook Express; use The GIMP instead of Photoshop. Perhaps most important in this is encouraging users to move away from Microsoft Office and its proprietary file formats and to use OpenOffice.org. This is particularly relevant now that the forthcoming OpenOffice.org 2.0 will use the OASIS OpenDocument XML format as the default file format:
The OASIS OpenDocument format is a vendor and implementation independent file format, and thus guarantees freedom and independence […] The OASIS OpenDocument file format is […] one of the file formats recommended by the European Commision.
This is pretty significant. Finally users have an option to use a full-featured office productivity suite without having their data locked in to a vendor’s closed proprietary file format.
Sadly, as this NewsForge article, Java fallout: OpenOffice.org 2.0 and the FOSS community, points out, the OpenOffice.org developers have shot themselves in the foot by choosing to implement a raft of new features in a way which is unpalatable (at best—at worst unacceptable) to the FOSS community, and makes it harder for ordinary end users to switch to OpenOffice.org.
Although the substantial new parts of OpenOffice.org written in Java are themselves licensed under a FOSS license, most users will need a JRE installed in order to use them:
- Sun’s JRE is not open source, and whilst it may be free to download it is not “free” in the sense required by most FOSS licenses. Many GNU/Linux distributions cannot and will not include it. For many platforms it is not even available. This means that those distributions will be forced to either
- refuse to distribute OpenOffice.org altogether;
- distribute OpenOffice.org with the components written in Java disabled;
- expend many many hours of valuable developer time attempting to compile the Java components into native code so that they can be run without a JRE.
- For end users wishing to switch to OpenOffice.org they now not only need to download and install it themselves, which in itself can be daunting for many users, but also download and install Sun’s JRE. OpenOffice.org is already a large application with a big memory footprint; Sun’s JRE is a notorious memory hog. The consequence of the former now requiring the latter is that OpenOffice.org will simply be unusable on many older low-end machines.
This has to be one of the worst decisions the OpenOffice.org’s project leaders could have made.

