Meeks: Measuring the true success of OpenOffice.org
Posted Oct 10, 2008 15:49 UTC (Fri) by
forthy (guest, #1525)
Parent article:
Meeks: Measuring the true success of OpenOffice.org
OO.o is not "sexy" for developers. What itch does it scratch what
a "real programmer" would need it for and therefore improve it? I write
my documents (papers, presentations) in LaTeX, using LyX as frontend if
appropriate. I draw my graphics still in xfig (inkscape would be an
option, if the developers would care more about technical drawings, like
better grid, component library, better arrows, and especially a user
interface which doesn't hide this deep in the attic, etc.), I render my
diagrams with gnuplot. And I can quickly write programs that massage data
much better than a spreadsheet. I tried oocalc for that purpose, but it's
sluggish when drawing graphics, and it's such a repetitive task to make
the calculations - I won't do that again (this is a fundamental design
flaw in how spreadsheets work).
Furthermore, a lot about OO.o is to make it work with Microsoft's
so-called "document formats". This affects design decisions within how
OO.o works - and especially affected them in the past. Reading and
writing a format full of cruft and legacy already makes a program bloated
and full of legacy, not a fun to work with.
IMHO when you dump a load of formerly proprietary code onto the free
software community, it won't take off. Or at least it requires that
everything is rewritten once or twice before people accept it (like
Firefox).
(
Log in to post comments)