Posted by: Anonymous Coward
on March 29, 2005 01:29 AM
Thank goodness there are plenty of alternatives to Sun's OpenOffice.
The point is that there is no need to search alternatives for OO.o - it can be compiled with Java disabled. It's not even necessary to do a full blown fork IMO - just implement the parts written in Java with e.g. Python and keep using the Sun codebase for the C++ code. Or use GCJ.
I think the best alternative so far is the one chosen by Ubuntu - ship a version where the Java features are disabled. It's not like any of them are essential.
Re:Time to fork I guess
Posted by: Anonymous Coward on March 29, 2005 01:29 AMThe point is that there is no need to search alternatives for OO.o - it can be compiled with Java disabled. It's not even necessary to do a full blown fork IMO - just implement the parts written in Java with e.g. Python and keep using the Sun codebase for the C++ code. Or use GCJ.
I think the best alternative so far is the one chosen by Ubuntu - ship a version where the Java features are disabled. It's not like any of them are essential.
#