Slashdot Mirror
OpenOffice 2.0 vs. Microsoft Office
Jane Walker writes "Slashdot's own Robin 'Roblimo' Miller compares OpenOffice 2.0 and Microsoft Office in a recent interview with TechTarget and, when asked to identify one of the main obstacles facing widespread adoption, calls for the OSS community to deliver personable, usable training for new OpenOffice and open source software users."
I do think the author is missing the point of Outlook in that for some people its just an email client and Thunderbird would work. What he misses is the shared calanders, remote mailboxes, offline working etc all which middle managers need to work. They stick with outlook as it has a good feature set for them. Users want things to "just work" and not have to worry about compatilbity or similar
SolarVPS - Quality Windows and Linux Virtual Servers
I know this is /., so we should all hate users and consider them to be morons.
However, in the real world, there are millions and millions of users of the Office suite, and a surprisingly large number of them are power users in Excel. This is where MS has a true mind share monopoly. There are so many companies that have invested literally millions of dollars in "development" of Excel models, macros and procedures. Telling those people to switch to an inferior product just because it's a bit cheaper is quite futile. (OOo is much cheaper in percentage terms, of course, but only marginally cheaper in terms of total savings per employee per year.)
Excel is the best software ever written for the mass market, by quite some margin. The rest of the MS Office products are OK with deficits (Outlook) or just plain bad (all the others, except Visio, if one includes that).
Getting people to move away from Word is probably quite possible. Likewise with PowerPoint, I'd guess. Getting people away from Outlook is obviously possible, considering that people actually use Lotus Notes (Ugh! I get a pain in my stomach just writing that...) No one uses the MS Office Suite becuase of Access. And no one uses MSO for any other of the programs.
Excel, people, Excel. Give us a superior spreadsheet and you will see it catch on like wild fire. Unfortunately, anyone trying will find that making a better spreadsheet is pretty darn hard...
Yeah, it's very poor indeed. But the reason is primarily, that even though the language is BASIC, the structures behind it all are really Java-like, and that brings with it a whole host of baggage. Users presented with an environment for programming in BASIC, will naturally expect a simple and easily understood object model to work with. As it stands, to use the OOo object model, you have to write pages and pages of the ugliest code, if you want to do even the simplest of things, largely because it's stuff that BASIC just isn't well suited to.
Was doing some data analysis and automation work using VBA in Excel for a client recently, and as I had a little spare time on my hands, and use OOo exclusively myself, I decided that I'd re-implement everything using OOo. I gave up.
It's not because it was difficult, although it's absurdly convoluted and finding the info you need to use the API is a pain in the arse, but because it would have taken at least 10 times as long to achieve the same results, and that was way longer than I had spare.
I've developed in some God-awful systems over the last 20 years, and even I looked at it and thought "I just can't be arsed". Can you imagine what a regular end-user with no programming experience is going to think?
Show them VBA for automating MS Office however, and even though they'll probably never really understand the full implications of what the simple commands they are issuing do, or the full extent of the object model, it doesn't matter. They work, and the commands they type just seem to make sense, they "read" right, and are straightforward enough to memorise and re-use.
What's really needed is a full re-implementation and extensive simplification of the object model, but obviously for a product as far along the path as OOo, that's not going to be practical. So, I'd personally suggest either a set of macros, possibly even implemented in OOoBasic, or the creation of a parallel API hiding all the messy nonsense and allowing users to interact with the suite in a similar way to VBA in MS Office. You need to get rid of all those cryptic Sun-isms like "com.sun.star.frame.DispatchHelper" if you don't want to scare off casual users.
Until this happens, nobody in a business environment is going to take OpenOffice.org particularly seriously. It's fine for individual members of staff just adding up columns of numbers and typing letters, but being able to automate things when your requirements go beyond that, is such a major thing even for many small businesses, that OOo won't get a look in until its macro facilities become significantly easier to use.