Language Selection

English French German Italian Portuguese Spanish

LibreOffice vs OpenOffice:

Filed under
LibO
OOo

Probably the most boring open source story recently is also been the one getting the most ink. The problem with with the Apache/OpenOffice saga is that the real story already happened, it’s history.

Oracle’s “gift” of OpenOffice.org to Apache, and the change of license from copyleft to permissive, is merely an epilogue referring back to a prologue: Oracle’s sudden ownership of the open source office suite as a mere byproduct of their acquisition of Sun.

The meat of this story, the chapters between, included Oracle stonewalling OpenOffice’s developers, the folks who collectively know by heart every bloated line in the application, how to improve it and, more importantly, how to fix it. This led to the resulting rise of The Document Foundation, the fork to produce LibreOffice and a first release only a few months later which was a marked improvement over the latest and greatest offering from OpenOffice.

This leaves us wondering, where does the story go from here, now that Oracle, at IBM’s prodding, has given OpenOffice away?

rest here




More in Tux Machines

Leftovers: Gaming

Leftovers: Software

today's howtos

ACPI, kernels and contracts with firmware

This ends up being a pain in the neck in the x86 world, but it could be much worse. Way back in 2008 I wrote something about why the Linux kernel reports itself to firmware as "Windows" but refuses to identify itself as Linux. The short version is that "Linux" doesn't actually identify the behaviour of the kernel in a meaningful way. "Linux" doesn't tell you whether the kernel can deal with buffers being passed when the spec says it should be a package. "Linux" doesn't tell you whether the OS knows how to deal with an HPET. "Linux" doesn't tell you whether the OS can reinitialise graphics hardware. Read more