StarOffice 6.0 Beta Available
Lumpish Scholar and 753 other people wrote in to let us know that Sun has released its beta of Star Office 6. CNET has a blurb about the release as well. I was hoping that Sun's site might be unclogged enough to try it out myself, but that doesn't seem to be in the cards today.
To all those who say 'Staroffice isn't 100% compatable, so we can't switch our office'. Well.. I understand the logistics and all.. but.
To switch to staroffice, you have to instruct your staff to learn to use it, and adapt the workflow to staroffice, not the other way around. The same goes for switching to any product.
The financial benefits of using staroffice in many cases outweigh the use of OFficeXP
All of the screenshots on the Sun site are of the Windows version. What does it look like under X Windows?
Seriously, there are few things that annoy me more than receiving a Word document from someone. Rarely, if ever, is there any justification for not simply using a plain old ASCII text file. They are smaller, platform independant and if formatted correctly, no harder to read.
StarOffice could be a strong competitor to Office if for nothing other than the price. At $479.00 a head, this adds up awfully quickly. Not to mention saving on upgrade fees in the future.
We shall see if corporations are ready to give up some functionality (admittedly, MS Office is still the one to beat there) to save on costs.
With MS raising the price, it might come to pass.
I like fire ants. They are very spicy!
Please note that Office (any flavor) does not take "scant amounts of ram". Rather, it hides ram used in the system memory used column, and actually preloads many if not most of the Office specific DLL's on boot up, whether you want them or not. The memory that appears to be used by Office, is only the glue code that links the DLL/OLE/NET components together.
The reason that Office appears to launch almost instantanously, is that most of it was already loaded on bootup.
Just a clarification...
jf
For instance, if I give someone a M$ Word document created on the Macintosh, the opening of that document will sometimes crash a windows machine. There is no reason for this as I am simply transferring a document from MS Word to MS Word. I suppose that such problems are tolerated because it limit the appeal of MacOS machines, and may indicate that I need to upgrade to the latest Office.
So, naive folks, do not wait for the day when MS Office documents will seamlessly integrate with Star Office. And do not blame Star Office for the problems. History provides nearly 20 years of evidence, all the way back to incomplete specifications for system calls in DOS, that M$ will do whatever it can to insure that integration does not occur.
Ximian is coming out with Evolution, which is essentially an open source Outlook replacement. It's still in beta but should be reaching 1.0 before the end of the year (I think).
So far, Evolution's main shortcoming is it doesn't understand Exchange protocols, so Linux clients can't use it to talk to Exchange for shared calendaring. I realize that is one of the main points you need. I believe it is a fatal flaw for evolution, but Ximian apparently doesn't think it's such a big deal, saying that such support will come "eventually, but not high priority". Nonetheless, it can do IMAP, POP, LDAP, and a bunch of other open protocols.
In a real emergency, we would have all fled in terror, and you would not have been notified.
It's nice to see some reasonable competition for MS Office. I alternate between Office2K and Openoffice (633) with reasonable success, but there are a few things left to complete the puzzle:
1. Where's the Mac OSX version? OS10.1 is getting great reviews, but this is even more critical from a general marketing standpoint than from a Mac-head view. Why? Cross-platform compatibility is a great marketing lever, not because of a possible massive platform shift (unlikely) but because of uncertainty about platforms and compatiblity over the long term. (See #4 below.)
2. Some major features are not quite there: imho outlining is the biggest hole; people who write large documents or like structure really need it. Instead of just copying the MS interface, perhaps the existing SO/Navigator tool could be extended to provide a killer structure interface similar to Framemaker+SGML. That would be pretty compelling. Likewise, a quickstart feature (as just implemented in Mozilla) would help to silence the yelps about quick startup ( after long preload) of MS Office XP.
3. Sun/OpenOffice needs migration documentation & tools. For example, it would be nice to have a short whitepaper from Sun that describes (or better yet, provides a one-click tool) that reconfigures MS Office to save in known cross-compatible formats. Word files should be saved in RTF or a reasonably-documented
4. Marketing!! Star/OpenOffice has such potential, and if handled properly, can deliver a very compelling message. I'm no marketing guru, but imagine turning some heads with these advert leaders:
Jon (insertmyslashdotname@jetcity.com)
I think not...(*poof*)
Do a /net install. Has been that way with SO since version 4.0 on linux (the first I used).
And it is pointed out several times in the detailed installation guide.
Sometimes I think the difference between computer gurus and guys like Lehtyos and other normal computer users is the ability and willingness to read a manual....
Moritz
When I started using Linux, I first used LyX for a couple of projects. Fortunately I tried out 'pure' LaTeX (itself a set of macros for TeX) and found it so much better.
There are several GUI frontends to LaTeX, one being LyX, and you can only harness so much power of the actual system via those interfaces. It's like coding C++ via a point n' click interface. You will only realize the point of LaTeX when using it natively.
Escher was the first MC and Giger invented the HR department.