Slashdot Mirror
Is it Time for Open Office?
lazyron asks: "I've been using Open Office a bit more lately, and got to thinking: this is much more like my current version of Microsoft Office than Office 2007 will be. Could it be time to try Open Office in the workplace, especially since there is still some time left before Office 2007 will be forced on us by the demands of the product cycle? Are there any IT admins out there thinking about trying Open Office, either with a few users or all of them?"
From a purely word processing standpoint, this is both the right and the wrong time for OpenOffice.org to challenge the MS crown. It's the right time because, hell, Word 2007 looks more different to Word 2003 than Writer does, on the surface of it. It's the wrong time because, finally, there is a worthy version of Word on the market. It has been ten years since the Office team released anything this decent and free of bloat. But for all those OSS nuts out there, yes, really, now is the time to push Open Office. A bit of serious market share for OSS is always a good thing.
OpenOffice.org is, in my opinion, the weakest part of the free software desktop experience. It is huge and bloated. It takes 100 MB - 200 MB to install (depending on your operating system), which is way more than it should. It doesn't use any platform's native graphical toolkit. Fonts look like crap in it. Etc, etc.
Honestly, I think that Abiword is orders of magnitude better -- not just in the obvious areas of size and memory footprint, but also in terms of the UI. It looks great in Gnome, and runs on Windows too (and it has a grammar checker!). I'm not a KDE user, but KWord also looks better than OO.o
I don't understand the fixation that people have with Open Office. It's slow. It looks bad. It retains all the things you hated about MS Office. The only things that it has going for it is that it has the most faithful .doc import of any open source office tool, and that it has the best ODT support at the moment. But the day that OO.o dies will be a happy day in my book.
#include ".signature"
To me this is one thing that makes Office 2007 great. With Word all the tools are right there easy to see in front of me. I didn't use a lot of stuff in previous versions because I never took the time to go digging for them. My fault, yes, but Office 2007 has removed my need to dig and makes it easy for me to access tools that I'm now finding to be pretty useful.
I love my sig.
Well, I do use Open Office in the workplace for about 60 users. They're factory users using terminals connecting to MS server 2003 terminal servers. Installing OOo was the cheapest way for the supervisors who needed to modify a couple of excel and word docs to legally do so. We had one file that wouldn't print correctly, so we installed excel viewer so the user could print that file. Other than that it's worked pretty well. The only app that gives us problems is acrobat reader, and that's always on one user's account. People working in the offices still have MS office installed, and that's not likely to change anytime soon.
BTW, I have many users still using Lotus 123 because of macros. I've given up trying to get people to convert to one app.
I'm a sysadmin, and "where's the support contract?" is a common mantra among management. However ... when was the last time _anybody_ called Microsoft for support with MS Office? Can anybody even name a single instance of this? I know I can't (granted, I haven't been in desktop support for ages, but I don't think most companies even bother to purchase a "support contract" for MS Office - they just buy the software and move on).
...
Anybody out there know of an instance of someone actually utilizing an MS Office (or any office software, for that matter) support contract? This argument strikes me as one that just doesn't hold water
illum oportet crescere me autem minui