An Early Look at StarOffice 8
polar_bear` writes "NewsForge has an early review of Sun's StarOffice 8, set to be released in mid-October. From the article: 'StarOffice 8 is not perfect, but it is an excellent value for businesses that do not depend on proprietary Microsoft formats for production work.'" And yes, for the uninitiated, NewsForge is still owned by the same parent company as Slashdot.
So, after reading the article, I didn't see any compelling features beyond what OpenOffice.org 2.0 promises. I saw several references to StarOffice's superiority over Microsoft Office 2003, but that's about it.
Me, I'll wait for OpenOffice.org 2.0. BTW, when is that, anyway?
I like OpenOffice on platforms for which it was designed to work (Win32, Linux), but it uses so many non-portable Linuxisms that it runs extremely poorly to not at all on OpenBSD, even with Linux emulation and Linux-style /proc enabled. That is to say that it runs, but consumes far too much memory and crashes frequently. And I'm too lazy to try patches from NetBSD pkgsrc or FreeBSD ports, so right now I've been using AbiWord and gnumeric in place of OO. They are fine, but don't do Office formats as well, and AbiWord generates really lousy postscript, which means that anything I print comes out looking like shit.
/proc, or not checking return values of functions that can fail, or making generally unsafe assumptions that just don't happen to come up on Linux. That's a sign of bad code. In defense of OO, it is fine to work with where it does work, and in some cases I like the UI better than MS Office. The best I can say is that it's come a long way since StarOffice 5, which ran poorly, even on systems on which it was designed to run.
(Please don't make this into a question of Linux vs BSD or free vs propriertary OS, that's not the point I'm trying to make.)
From a usability perspective I like OpenOffice, but I wish it were more portable. In my mind, if a program uses too many Linuxisms that don't hold on other Unix-like systems and require non-trivial patches to port, it is a good sign that the code is poorly written. I.E. it's doing stupid things like relying on Linux-specific values in