OpenOffice Illustrates Open Source's Limitations? 611
Cardbox writes "In his latest article in The Guardian, Andrew Brown asks 'If this suite's a success, why is it so buggy?'. OpenOffice, he says, shows the limitations of the open source development model. Brown is not your usual ignorant Microsoft-bribed hack. He has himself contributed macros for OpenOffice users. Brown lists the problems and assigns causes. He adds: 'If OpenOffice3.1 becomes a blockbuster... it will be because large companies such as Sun, Google, and IBM have decided that open source is the cheapest way to gang up on Microsoft, because it means they need spend nothing on support.'"
Alternate (Score:5, Funny)
Large, complex pieces of software, generally have bugs, becuase they are large and complex.
Re:Alternate (Score:3, Insightful)
The rest is some rant about OS people saying users can submit bug patches but hardly anybody does.
Re:Alternate -- only 2 bugs mentioned (Score:4, Informative)
I have found a few bugs/missing features I would like to have. For example:
-in Impress, so far there is no way to embed sound or other multimedia files. In PowerPoint I used to do this. I would like to be able to have a music file play while the slides autoadvance. I can do the second part easily, but I can't get sound to play. I also have not yet been able to embed a short film clip on a slide.
-in Writer/Calc/Base there is no easy way to print mailing labels from either a spreadsheet or database mailing list. The help files give a method to do it, but when the method is followed only the first page is formatted making it necessary to repeat the process several times if multipale pages of labels are needed, such as for a large database.
-Impress tends to crash often for me during formatting/creation when my slides have a lot of photos (like if I want to make a slideshow of jpgs/pngs/etc.)
There might be more, those are off of the top of my head less than two minutes after reading the OP and link.
Disclaimer #2: I use Linux exclusively (Ubuntu) because I want to--not because I hate any particular OS or company. I have other very effective methods of producing the mailing labels I need, but I would like a good presentation program...Impress is almost there.
Re:Alternate -- only 2 bugs mentioned (Score:5, Informative)
Insert -> Movie and Sound.
Quite easy, isn't it? If the format is unknown, then do the following (from the OOo help system): "On UNIX systems, the Media Player requires the Java Media Framework API (JMF). Download and install the JMF files [sun.com], and add the path to the installed jmf.jar to the class path in Tools - Options - OpenOffice.org - Java."
HTH!
Re:Alternate -- only 2 bugs mentioned (Score:5, Insightful)
That's the bug.
As Edward Tufte noted, "PowerPoint Makes You Stupid." And trying to make your dumbass slide deck into a mulimedia extravaganza makes sure everyone knows it. And that goes for other presentaion software, too.
Re:Alternate -- only 2 bugs mentioned (Score:5, Funny)
And there are many legitimate situations on which to show a short clip, for example in education. Nothing augments a presented experiment more than the lecturer in his youth with long hair and beard, stumbling around in a small lab.
Re:Alternate (Score:5, Insightful)
The spell checker essentially receives a D+. After I'm done writing a few dozen page paper, I have to paste it into MS office for because Open Office misses too much.
Firfox, for example, is receiving great press because it is a great product. It covers all the simple things. Open office is ok for the basic. MS Office is great for the basics. I'm not reviewing the advanced features here: The face of the product is what the majority of users review.
I still support Open Office though. And I will still use it. But I'm not going to say it is better than MS office. It comes close, but still has to simplify and reduce.
Also, the author of the article is way off the mark to flaw the open source movement as a whole just because of Open Office's shortcomings.
Re:Alternate (Score:5, Interesting)
I have a similar view of OpenOffice to you, I think. I'm grateful to those who choose to give it away, because it helps me to do some things I'd otherwise find inconvenient without paying for software since I don't install illegal copies of commercial products. However, I have no illusions about the power or quality of the product, nor its overtaking MS Office in any significant way any time soon.
In fact, without wishing to seem ungrateful, OpenOffice doesn't really have much going for it over its major commercial rival at all, other than being free-as-in-beer. There are countless useful ways a word processor could do better than Word, making real people more productive at real jobs or giving nicer output for jobs they already do, yet in five years of Microsoft not really addressing any of the issues, the open source world has failed to do anything particularly innovative, preferring to play a never-ending game of catch-up with the market leader.
What I really wanted to challenge, though, was this statement in the parent post:
Perhaps, but look at it this way. We know, just by looking at popular OSS sites like this one and the download stats from OSS web sites, that OSS provides a few big-name, mass-market products: Linux, OpenOffice, Mozilla et al., that sort of thing. It also provides a wider range of fairly established tools for more specialised niches. And then it provides mountains of rubbish, most of which never gets to version 1.
Now, the list of advantages given by advocates of the OSS approach often starts with things being less buggy and more secure, on the basis of the "many eyes" principle mentioned in TFA. This claim is usually backed up by citing the relative scarcity of security breaches in Linux-based systems, the relative immunity of Firefox to nasty web pages, and so on. OSS is also claimed by some advocates to produce more innovative software, basically because the developers aren't tied to company conventions, can adapt faster to changing requirements from users, etc.
However, if -- as the author of TFA argues based on actual bug and feature request data -- you can't necessarily rely on user support to improve a product even for probably the largest and most widely used products of the OSS world, that blows that whole argument out of the water. OpenOffice isn't less buggy than MS Office, nor innovative in any serious way; it's a near carbon copy of the established commercial player, a few years behind the times in features and robustness. And if the OSS approach doesn't achieve the claimed benefits for OpenOffice, why should it provide any advantage for smaller products with smaller user bases?
To an extent, there is a genuine answer to this question. As I've discovered myself, the code base for products like OpenOffice and Firefox is simply too big for a keen amateur to get stuck into within a reasonable period of time. Just downloading the source and getting a build set up is often a chore for the many of us who are running Windows boxes, because so many products tend to be built using GCC on Linux or something similar. Smaller, less unwieldy projects might fare better here. But then again, does something like OpenOffice or Firefox really need to be the size they are, or is the source just bloated as a result of the less structured development processes that are inevitably used when software is being built by a constantly varying and geographically diverse group of volunteers?
In other words, while I agree that it's unsound to generalise too much from the author's factual data on a specific OSS product, that product does offer a pretty solid counter-example to the usual arguments advanced by OSS evangelists for the superiority of their approach over traditional closed source, commercial development.
Re:Alternate (Score:5, Insightful)
Maybe what we need to be asking is not "If Open Source is good, why is it so buggy" but "If proprietary software spends 100 times the resources to produce a 10% better product, who has the better development model again?"
Re:Alternate (Score:3, Interesting)
That depends on whether that extra 10% makes a difference to how well you can do what you need to do, I suppose.
FWIW, my experience is rather different to yours: whether you call them bugs or usability issues, I find quite a lot of the non-trivial functionality in OOo is bizarrely har
Re:Alternate (Score:5, Interesting)
The fact that OpenOffice (an especially poor choice of OSS poster child, but whatever) is even within an order of magnitude of Office (with literally hundreds of developers and tens of millions of dollars behind it) is simply astonishing.
Not really: most of the development happened when it was a commercial product (which had a fairly large niche market in Germany, AFAIR). For me, the damning thing about the whole OO saga from the OSS point of view is how little truly revolutionary has happened since Star Office went open source.
And before all the OSS groupies throw a hissy fit, have a look here [firstmonday.org] for Linus totally agreeing with the statement
Re:Alternate (Score:3, Interesting)
I am not very knowledged with regard to printing frameworks. But would it be possible for a PDF exporter implemented as a virtual printer to still do things like creating table of contents, provide clickable intra-document links as well as clickable external hyperlinks?
Re:Alternate (Score:3, Funny)
Firfox, for example, is receiving great press because it is a great product.
I see what you mean.
What 90% of the bugs were... (Score:5, Interesting)
You can't really blame the OOo team for that, can you? It's hard enough to create an open, expandable format but then to have to convert a closed-source, purposefully obfusticated format (.DOC) to your own (.ODT)...? Can ANY of you name a single non-MS related program that handles
Folks, there have been documents written many years ago in the 3.1 versions of Office that a user here couldn't read with Office XP and yet OOo managed to read them just fine. Then you've got the Wordperfect conversion stuff, the PDF and Flash exports, etc. I'd say the team has done an excellent job with everything - especially when you see the original code (StarOffice 5).
I don't doubt that much of what the article's author says is true. Sometimes it seems that development is moving at a snail's pace. But I'd rather they do that than have them release something clearly not ready for prime time. I'd say they accomplished a great deal of refinement and polish with 2.0 and am really looking forward to the great bibliography project slated for inclusion with OOo 3.0.
Re:Alternate (Score:3, Insightful)
Do you just regard anything that is critical of something you love as flamebait? That isn't a very productive approach.
"The rest is some rant about OS people saying users can submit bug patches but hardly anybody does."
Re:Alternate (Score:5, Funny)
Re:Alternate (Score:5, Insightful)
There is a tremendous and powerful set of server tools such as Apache web server, the aforementioned Perl, PHP, MySQL, and all the thousands of Unix/Linux command line programs that are used to run most of the world's servers. You would hardly expect Andrew Brown to complain of how limited and buggy Apache Web Server is and how much better Microsoft IIS is, not to mention Linux and MySQL and Perl/PHP--a laughable claim that would not be supported by the facts. This seems to sink his thesis; LAMP is the server to beat and has been a thorn in MS's side for years and are really your classic opensource, community-developed and supported applications.
I think it would be more fair to look at the bigger picture. Open source and public domain software pretty much dominates the back end, and on the front end Windows software rules. Yet, recent distributions of Linux are getting increasingly solid and easy to install and use. Recent versions of Firefox and OpenOffice and Gimp pretty much do everything any user will ever need, are solid and featureful and under constant development and improvement.
I think Brown is a bit impatient for the future to be here now. Is there room for improvement in the OSS model? Of course. Wait another year or two and (as he himself points out) version 3.1 of OOo will surely be fantastic, along with Linux kernel 2.8 and Firefox 3.5 and on and on. After a certain point, no commercial software will be worth the hundreds of dollars differential; the user experiences will be too close to call. There will be a natural shift away from Windows lock-in and we'll be buying our $100 laptops running Ubuntu or Suse or Fedora while Microsoft scrambles to be the next Google. Should be an interesting next five years or so.
Re:Alternate (Score:4, Insightful)
Sun sells StarOffice for support. Sun writes most of the code for OpenOffice and this code is used in StarOffice. Obviously Sun is in exactly the same place as Microsoft in terms of wanting to minimize the number of support calls.
Also a 100 full-time Sun employees is nothing to sneeze at. I don't need a more complicated OpenOffice for 3.0, I'm happy if most of the improvement (for a while anyway) is in speed and fewer bugs. 100 employees can do a lot of code optimization.
Dara
- I wish Sun had gone with SunOffice for their version and left the StarOffice name for the open source version -
Re:Alternate (Score:4, Insightful)
Like hell he does. He is specifically singling out "programs intended for use by the non-programming public", which end up being supported by a very small group of people. Exactly how much of this article did you end up actually reading before you decided you disagree with his conclusion so there is no use considering his arguments?
Re:Alternate (Score:5, Interesting)
And there are plenty of projects that are "intended for use by the non-programming public" that are twenty times smaller. Heck, the open source poster child Firefox is twenty times smaller (assuming binary size roughly correlates with size of code base, which should be fair). Brown raises some interesting points, but I think many of OpenOffice's problems really are unique to OpenOffice.
Re:Alternate (Score:3, Insightful)
Re:Alternate (Score:3, Interesting)
No we have to agree the RMS is one of the noisiest and most visible to the unwashed masses; rather like Firefox and OpenOffice. Perhaps we should promote these projects as corporate open source projects rahter than the more commonly percieved community open source projects.
Re:Alternate (Score:3, Insightful)
From my perspective, this is the "closed" portion of the open source movement, with the mindset that no commercial software, be it a Photoshop, AutoCad, Quicken, or an Oracle, has any place whatsoever. Personally, I pay for value received, and I value professional-grade tools. If FOSS has a viable alternative, then fine. If not, then that's fine too. For many of my uses, I don't want "good enough", I want, need, and demand the best.
Too many people let th
Re:Alternate (Score:3, Interesting)
OO is an absolutely *huge* and complex project that nobody but the "elite" can really program and I think that is no secret. Crap, I have been using Unix/Linux for 17 years and couldn't even get OO to *compile*. But Stallman's premises *do* work for much of the Open Source world. Even
Re:Alternate (Score:5, Insightful)
Maybe because it's not so buggy? Whilst nothing will be bug free it's kinda moronic to see the same bullshit modded +5 funny day in day out along with the BSOD jokes in 2005 and clippy jokes. They really aren't funny to the majority of people who will find the current MS OS stuff to be pretty stable assuming their not stupid enough to open freesex.exe and whatever else. Cue for someone to tell me their stories about spontaneously combusing registries that always seem to happen to MS haters.
Re:Alternate (Score:5, Funny)
Here goes!
Okay, so one day I was using my PC, right? Needless to say it runs Windows, because all serious computer users use Windows. Microsoft has a monopoly and we have no choices. You can't buy a good alternative, so you might as well just give up the idea of downloading one for free!
Anyway I was sitting on my ass, browsing for porn, eating pizza, smoking cigarettes, and drinking beer like any good computer geek when suddenly I smelt something burning. No, it wasn't a cigarette that I hadn't put out. It was something worse. MUCH worse! What I smelled was the unmistakable scent of a burning REGISTRY!
That's right! My REGISTRY had caught on fire! As with all major Windows problems, I immediate ran to the one fool proof solution. I hit my ever useful Windows key, brought up the start menu, then moved my mouse mouse pointer over to Shut Down because what I needed a RESTART, and FAST! That always solves everything!
But before I could select Shut Down, some obnoxious program stole focus. It's this program you may have heard of, called Outlook Express! I had a new e-mail! Clearly in the preview pane I could see an e-mail with an attachment, but before I could do anything my antivirus software popped up a warning telling me that my registration had expired and if I wanted to protect my system I needed to pay $49.95!
I felt my mouth go dry and my stomach sink, I knew what this meant! I needed to run an antispyware program! Unfortunately I was unable to do anything at this point because I bought my system at Wal-Mart and the hard drive was grinding away trying to respond! It was so obvious that my system was not going to respond that my Window even said "NOT RESPONDING!"
Then it happened. Windows asked me if I wanted to report a bug. I thought "that's very thoughtful of them, I'm sure Microsoft will get right on with fixing my problem" but before I could send the bug report the screen when blue and filled with a really cryptic message.
I had been through this a dozen times, and knew at this point the reset button was the only remaining option. As I reached for the system it just exploded. Bits of plastic were thrown everywhere, and one even got stuck in my eye.
So that's why I tell people we need band together and search for some kind of alternative. Something different, free, stable, or all of those things. Tell everyone you know. Microsoft really suck, and I only have one eye to prove it!
Was that what you had in mind?
Re:Alternate (Score:5, Interesting)
Now, compare this to codebase for OpenOffice, which while almost as old as a product as MS Word, was purchased by sun about six years ago, and only has been open sourced for 5. Factor in the time for new management, new developers, and new priorities, and MS Word has a significant advantage. The advantage for MS Windows over Linux is even greater. This is not even counting the massive resources that MS can throw at a project. Just look at XBox. In fact comparing Linux to MS Windows is like comparing MS Windows to Mac OS. In both cases one has a latecomer to the market compared to a forerunner.
For the record I used MS Word on many platforms up to a few years ago. I moved to openoffice.org because the feature set was complete enough, and was reliable enough. Continuing to use MS Office was not even worth the minimal cost of an educational license. I don't find it any less reliable than Office, and certainly has no problem opening up the Word files I recieve. In education one regualarly recieves word files from many different versions, as many people use older machines.
Re:Alternate (Score:5, Insightful)
Re:Alternate (Score:4)
Re:Alternate (Score:3, Informative)
http://developer.berlios.de/projects/lyxwininstal
Re:Alternate (Score:3, Insightful)
MS-DOS was a key component in creating the commodity personal computer - or at least commoditizing the hardware piece of it. And because it was a key, Microsoft rode the wave of commodity PCs that washed over the Industry (it should be noted that IBM set that wave in motion). Windows comes in as a partner (and later "replacement") to MS-DOS as a continued key component to cheaper, more open PCs.
Wi
Re:Alternate (Score:3, Interesting)
>on the desktop market, like Windows displaced Apple?
Windows never displaced apple on the desktop, IBM PC and the clones (running *DOS*) overtook apple 2. Even when the macintosh with Mac OS came out, people still preferred the command line DOS over a state of the art (at the time) graphical interface. Apple *never* caught up with PCs again.
It just means that there are many other important factors, it's not just a question of
Comment removed (Score:5, Interesting)
Re:Alternate (Score:4, Insightful)
A project like OO is huge, and a lot of the work that really needs to be done is boring as hell, not visible, completely unsexy and thankless. Doing maintenance work or squashing a bug that nobody will ever thank you for is just not going to attract developers. So the bugs remain while the features march on, and all the while the product becomes more and more bloated and unusable.
You can see the same pattern elsewhere - look at Kdevelop. Great, great development environment. Infested with piddly little bugs. Small stuff, like it won't save settings reliably, or it crashes with XIM, or whatever - but the environment has every feature you could ask for, and more are on the way!
Is that a condemnation of OSS? Nope, but it's something that the community has got to deal with - as the article points out - and probably sooner rather than later. How that happens, I do not know, because even in companies that are paying people to write code, it's rare to find someone who actually wants to get in there and do the grunt work when there are sexy new features to work on.
Re:Alternate (Score:3, Funny)
Re:Alternate (Score:3, Informative)
Now, I might have it a little unfair. I'm competent enough when it comes to Windows that unless I do something dumb to screw it up, (details we can leave out) I rarely have t
Re:Alternate (Score:4, Interesting)
Hell, I've only rebooted my current XP machine twice - once to install a video driver update, and a second time when a game crashed the same driver. XP didn't even go down during that crash - it apparently switched itself to a generic driver and gave me a dialog explaining the situation and recommend I reboot to fix it.
As a matter of fact, the only blue screen I've had in the last three years was a dead DIMM. I'd call that a fair reason for the OS to go down. Actually, I'd be pissed if it didn't under those circumstances.
Re:Alternate (Score:4, Interesting)
I've installed Office 2003, VirtualPC, Windows Media Player 10, Visual Studio 2005, and more... all without rebooting. Even the last version of Symantec Anti-virus I installed didn't want to reboot until after I had run LiveUpdate, and that was because it couldn't replace some Symantec files because they were in use. Nothing to do with Windows.
Most (decent) installers don't require a reboot anymore. The place where you'll still see them are when the program intertwines with the OS or is trying to modify something which is locked by the OS or another (misbehaving really) application. Even most newer Windows Updates don't require a reboot, depending on what you're doing when you run the update. If you've done as suggested and closed all running apps then the odds of needing to reboot are less.
It's important to remember that one reason Windows needs to reboot more for system changes is in part because of the file access model it uses. On Linux, stuff is loaded into memory and the file is pretty much ignored from then on. In Windows, when a program is using a file or the registry it can (and by default does) lock it to prevent other processes from modifying it.
I saw a comparison once (can't find it now) showing what happens if you run the commands "rm -rf
Anyway, the point is that as the consumer line of Windows has grown into the NT kernel it's gotten better and a lot of things including stability, uptime, and rebooting. Unfortunately the old 9x, NT, and 2000 claims of all these problems simply won't go away along with the old versions of Windows to which they were tied.
Re:Alternate (Score:4, Insightful)
Ermmm... correct me if I'm wrong, but wasn't Windows' success based on Window 95/98, which were both buggy POS's (except for 98SE)? The GP poster has a point when you consider Microsoft built up an monopoly on the basis of a bug-ridden often-unstable OS.
(Posted from a Win2000 system with an uptime in the months - I accept you have a point, but Windows' success came *before* the stability of the 2000/XP editions).
freesex.exe? (Score:4, Funny)
Re:Alternate (Score:3, Insightful)
I have auto-update active on all machines. i have antivirus, spyware, and adware programs running on all machines. None crash, none slow down, none are infected. And all of my machines were cheap. Dirt cheap.
I use firefox; I agree that internet explorer is a shitty browser.
The reason the average computer user doesn't switch off MS is because there is no reason t
Re:Alternate (Score:4, Insightful)
1) no word wrap in comment boxes
2) spaces don't show up at the end of a line
Number 2 I see often in word processors in order to perform word wrap properly, so I'm not sure what he's talking about. Number 1 seems minor in comparison to the enormous bugs in Office on things as simple as page numbering and wrapping text around a picture.
Also, he doesn't consider that the restrictions on OOo code may be keeping some programmers away since they have to sign everything over to Sun.
Also, to be fair, an office suite is a giant, unweildy, unUNIXy type of program. Digging through the monsterous codebase is a high barrier to fixing a bug that may just be a minor annoyance. An office suite would have to be broken into much smaller parts in order to encourage more people to develop the software.
Re:Alternate (Score:3, Interesting)
The big question is, if we can easily and quickly make a world class word processor, how do we make it? Do we mindlessly ape Word down to the las
Re:100 times longer (Score:3, Insightful)
No, OOo loads spreadsheet files fully into RAM while Excel only loads the part which is currently being worked on. The result for extremely large spreadsheets is that OOo is slower than Excel.
This is a pretty good example of how the FUD and astroturfers work. You analyse the competition for an area where your own product has a theoretical advantage, then just refer constantly to the competitor's flaw as thou
Atlest some fair comments against Open Source (Score:2, Insightful)
Re:Atlest some fair comments against Open Source (Score:4, Insightful)
Staroffice was made public in 1986 and made OSS in july 2000. Its length is cca 10mio lines of code. It has made a lot of progress in last 5 years. Especially if you take the project length to account. And Staroffice had a lot more problems. It acted as complete desktop, which OO.o rid off. Bad language support. Even longer start times. A lot less functions.
Again, how hard is "many eyes" to make bigger and better result differs on few factors.
- was it always OSS? It is harder to maintain something you've not written
- how big it is? OO.o scales as very large project here
- How many eyes? In fact not so many as one would thought.
Taken these point to account I dare to proclaim OO.o is a success with a great future.
not open from the beginning (Score:5, Insightful)
Re:not open from the beginning (Score:5, Insightful)
Firefox/mozilla another example. (Score:5, Interesting)
By the time that Mozilla inherented the code base.. it was a mess. It took years and years and years of constant developement and change to massage it back into a state were it was a superior system to IE.
Then it took even more development on top of that to get it to the point were you had good/attractive UI design in the form of Firefox, Thunderbird, etc etc.
And all of this was done at a fraction of the cost compared to things like IE.
Then you have konqueror and such that didn't have a legacy code base to deal with and they pumped out a nice browser themselves in a smaller amount of time and probably with a even smaller budget.
And anyways.. if OO.org 3.1 does kick ass, and even if it is still done with help from IBM/Google/Sun/etc etc doesn't that mean that the open source still works?
None of those companies by themselves would be capable of competing with MS on MS's own terms. (basicly document and feature and user compatability with MS's office on MS's OS in a MS dominated market)
Re:Firefox/mozilla another example. (Score:5, Insightful)
And Open Office is crap because, basically, Office Suites suck, and they are just following the trends.
OOWriter is a slow clone of Word. Word sucks: unpredictable pagination across sessions/computers/platforms/printouts(!), primitive typesetting, asinine default settings.
At least OOWRiter can make PDFs and has acceptable default settings.
What would really make a splash is an open-source approach to word processing (or the whole office suite idea) that is better than the ugly, intrusive, slow, WYSIWYG implementation that Microsoft offers.
This isn't a polemic for LaTeX, but for a new kind of word processor, even office suite. Once you show people why Word sucks from a user experience perspective (and not just an idealist, technical, political, or economic, perspective), many will switch.
We need a wordprocesser that encourages semantic layout. I'm talking about templates that are easy to use, not hidden, with accessible formatting controls (think WordPerfect reveal codes).
Re:Firefox/mozilla another example. (Score:5, Interesting)
I've been making your argument for years, but alas never convincing anyone with the resources to have a go.
I think a combination of making the use of stylesheets the default and (shock!) not even putting manual formatting controls on the toolbars and such by default would make a huge difference. Make the menus and toolbars very simple, with only the major commands directly related to writing easily accessible, and let the powerful, flexible but easy-to-misuse things be the ones only power users can find.
Obviously this can't happen in isolation. For a start, it would require extensive usability testing to determine fast and easy to use interfaces to configure the styles themselves, store them for future use, construct template documents etc. This sort of thing is often a chore in today's applications, yet I see little reason it should be more than a couple of clicks or a quick shortcut key to do most of it, if the UI places the emphasis on the right ideas that support it.
Re:Firefox/mozilla another example. (Score:3, Insightful)
As it was, Mozilla shipped in an extremely buggy form (Netscape 6) and didn't become acceptable to users until 2004
So, Better? Yes. "Smaller amount of time and probably with a even smaller budget"? Absolutely No.
And all of this was done at a fracti
Re:not open from the beginning (Score:3, Insightful)
But OpenOffice.org is typical of OS projects that have "brand name" recognition among end-users. In this market, the cathedral model of corporate funding and control is still very much alive.
Re:not open from the beginning (Score:3, Interesting)
Not to mention that half the comments are in German.
I'm a native English speaker, and my German is pretty good (all of high school + a few years in college), and I can't figure out that crap.
Many eyes make bugs shallow, true, but you can always find ways to sink it. Putting the source in two separate (spoken) languages is a pretty good one.
Openoffice is special in that its barrier to entry is higher than an
Re:not open from the beginning (Score:4, Interesting)
You deserve the insightful moderation. I was a StarOffice user (even paid for it) and I have found OpenOffice to be significantly more stable and less buggy. If anything, OpenOffice proves that the open source model works and the closed source model (that produced StarOffice) does not.
And what about Linux? (Score:5, Insightful)
Re:And what about Linux? (Score:3, Informative)
The difference is that Linux is undergoing massive development compared to the BSDs which are making more incremental changes. But most of the Linux eyes are on new code, not on stabilizing current code.
You missed the point (Score:3, Insightful)
I don't entirely agree - but that hardly applies to Linux. Try come up with another example, I'm sure there is one out there.
The obvious question (Score:4, Insightful)
All I know is, MS Office is almost physically painful to use for anything more complex than the simplest tasks. If OpenOffice can beat this "standard," it's doing well.
Re:The obvious question (Score:4, Interesting)
I'm not sure them being open is enough either. I like the idea of tinkering, and I even do that from time to time, but it's icing on the cake.
They are better, so much better that it's laughable to think that people still struggle with windows and IE.
OpenOffice does not come anywhere close to that. Being slightly better should not be the criteria we aim for, and it shouldn't be enough to deserve all the hype we're giving it.
Bloat... (Score:2, Insightful)
There's just not many eyes. (Score:4, Funny)
It's just there aren't many eyes in there.
I think I saw some GNOME developer on the street corner, with a cardboard sign that read: "Please, please, PLEASE work on OpenOffice? Pretty please?"
Depends. (Score:3, Insightful)
How about gnome? (Score:4, Interesting)
I think that it makes absolutely no sense to project open office on all open source.
Partially correct, I'd say. (Score:5, Interesting)
That being said, yes, OOo is pretty much crap and utterly useless for anything beyond basic office duties; its spreadsheet capabilities are laughable at best (no simplex or network model solvers), and what's an even bigger kicker (for me) is that you can't really use it on OS X!
Sure, you can run it in the X11 emulation layer, but one of the reasons I bloody switched to Apple was that I was very tired of dealing with X11 being useful only for displaying terminals. Why would I want to run X11 when I finally escaped from it? Oh, and if you do run OOo under X11.app, you don't get any of your local TrueType fonts (IIRC), or any of the integration that makes OS X so much a pleasure to work with, from a desktop perspective.
Don't get me started on NeoOffice. It's maintained by two guys who have better things to do with their time, and still suffers from the shortcomings of OOo, as well as some integration problems (i.e., it doesn't even use the native printing or file dialogues).
But these problems are endemic on a per-project basis; Firefox is an overall fantastic program, LaTeX is great as well, and libgaim powers AdiumX, which gets a lot of use on my system.
But someone has to come along and make something better than OOo; I've half a mind to do it myself, when I'm finding myself not working full-time as a UNIX sysadmin while going to school full-time.
Re:Partially correct, I'd say. (Score:4, Insightful)
Yeah, if it wasn't for mean ol' Sun, there would be programmers lining up around the block to work on spreadsheet macro code and contextual help menus for free!
Or maybe, Sun does all the OOO dev because, frankly, nobody else would.
Re:Partially correct, I'd say. (Score:3, Interesting)
you are wrong on two counts:
count one: there was a dual license scheme where YOU got to choose which license to submit your code under, one the SISSL the other LGPL.
count two: the license changed recently [desktoplinux.com] to pure LGPL
OO.o isn't buggy for me (Score:3, Informative)
Some inherent problems (Score:2)
Rubbish (Score:5, Insightful)
It's wierd because it spent the first 90% of its life as a closed app. And it shows. Remeber when netscape released their code and the open source world had to basically start from scratch writing gecko because the code was so (dare I say it?) awful? Well OO.o is a project that is several times the size only they haven't had the opportunity to do a rewrite. On top of that it's mainly written by three (traditionally closed development) companies who are trying to pull it in slightly different directions (Sun, IBM & Novell).
Contrast with open-from-the-start projects such as koffice, abiword and gnumeric, which are generally accepted as being much better behaved, even though they might not have all of the features.
Re:Rubbish (Score:5, Interesting)
Closed source produces a lot of good code, but you never get to see it (unless you work on it) becuase it stays closed.
Re:Rubbish (Score:5, Interesting)
Really? Because I have worked for a wide variety of closed-source companies over the last 25 years, and I have seen very little of this "good code" you refer to. One of the things that seriously attracted me to open source/free software in general was the much higher standards of coding that most of the developers seemed to adhere to.
Of course, maybe things have improved since I dumped Windows for once and for all back in '98, but somehow, I find it unlikely.
Ok with me (Score:3, Insightful)
It's because OO Isn't an Open Source Project (Score:5, Insightful)
I think some of this has historicaly been a trust problemn, and some has been their copyright assignment policy (which is also a trust problem).
Thanks
Bruce
Re:It's because OO Isn't an Open Source Project (Score:3, Interesting)
Re:It's because OO Isn't an Open Source Project (Score:5, Interesting)
Yes. To get the full benefit of Open Source, you need a big enough community to drive work for many different agendas rather than mostly one agenda. The problem is tha OO is still mostly Sun. If this were GNOME, for example (which is a project upon which Sun shares work as am equal partner with a large community) quality would be higher.
And all of this makes me sad because the program is so important to the Linux desktop.
OO is Open Source because it's Open Source licensed. The OpenOffice project falls somewhat short of achieving all of the benefits of an Open Source project due to a lack of community, and that in turn is due to some of Sun's decisions about the project policies and about their corporate communications concerning Open Source over several years.
Bruce
Re:It's because OO Isn't an Open Source Project (Score:4, Insightful)
It really bothers me to see people keep focusing on OOo as if it were the holy grail of the Linux desktop, instead of one of many possible roads towards a fully functional office suite. When I need productivity apps on my linux desktop at work, I don't immediately fire up MS Office or OOo, but usually something from KOffice. Yes, there are times I can't because I know the featureset I need isn't there but when that isn't the case I do launch it, because it offers a much nicer user experience under KDE.
My point with this? OOo is quite possibly a dead end, and having wildly visible open source evangelists shouting its name from the hilltops doesn't seem to be parting the Red Sea to open a path to the Office Suite Holy Land. Perhaps instead if they started exhorting the hordes to understand the limitations of KOffice, or AbiWord, or Gnumeric, or any other genuine F/OSS productivity app whenever possible, to submit real bug reports and real feature requests then perhaps a real road forward might just show itself.
Honestly, this might even be the spark that ignites the fire that saves OOo. Remember when KDE was the only really functional desktop environment under X11? Remember how everyone with a real belief in F/OSS screamed about the restrictive licensing of Qt? Notice how now we've got two highly evolved, and several up and coming, desktop environments one of which was massively relicensed to be more in line with the needs of its user community? Lets stop beating dead horses and start finding solutions. We've done it before, and we can sure as hell do it again.
Part of the supposed credo of the F/OSS movement is that its always a meritocracy, and OOo just doesn't win under that system. Lets stop propping it up like a South American puppet state, stop explaining away its flaws, stop making ourselves look blind to reality with our zealotry. Also, for damn sure, lets stop nitpicking articles and missing the point.
Re:It's because OO Isn't an Open Source Project (Score:3, Interesting)
German comments aren't so hard to figure out. "puffer" is "buffer", and we have machine translation these days, so I'm not so sure that's the
Re:It's because OO Isn't an Open Source Project (Score:4, Insightful)
I don't disagree with the statement but I think you might like to find another term to replace "Open Source Project". You're drawing a fine line between Open Source software and an Open Source project; where the first refers to the licensing and the second refers to the development model. It's too semantic and will lead to unnecessary confusion.
Re:It's because OO Isn't an Open Source Project (Score:3, Informative)
Evolution and Nautilus had the heavy lifting done by Ximian and Eazel, but both projects were carried out as subsystems of the larger GNOME project, rather than as stand-alone Open Source projects. My impression was that the larger GNOME community was involved, if not actively collaborating, that the intent was always to have the GNOME team accept those
Re:It's because OO Isn't an Open Source Project (Score:3, Informative)
Sorry, but IBM only started out as the primary developer. The Eclipse Foundation is now substantially more than just IBM. [eclipse.org] There are
Word Count! (Score:3, Informative)
>>
I have written numerous macros (which automate less obvious, or screamingly obvious, tasks), including the word count for version 1.
Not to detract from his points - bringing more focus can't hurt in the long run - but around 1.2 days I surfed the bug database and found an amazing number of bugs relating to
I wondered what was up with that. I was more concerned about printer bugs and other bugs. Rather funny to see him raise that flag though.
Twiddling under the hood! (Score:3, Interesting)
I've seen these same types of issues when I worked for Ashton-Tate. We had 100+ developers working on dBASE IV. And what did we release? A bug filled application that induced the death of the company. Meanwhile, a group of 6 developers worked on a dBASE compiler environment that worked great! Seems the more developers you throw at a project then the less communications between them and the more bugs you end up encountering. I would hate to see this happen with OO. But then, if the project managers keep a good handle on it, then the rest of us "end users" will be quite content and happy to use OO instead of the bloated MSO products.
Tim Trimble
The ART of software Development
don't believe it (Score:3, Insightful)
ok, OO isn't on a par with MS Office for functionality- but then as many have pointed out, the average person doesn't need the extra stuff that MS Office does. and the article didn't mention that ms office has it's quirks too; i can never get it to format tables the way I want to, and trying to get a document to look the same in different versions of Word is a non-starter unless it's extremely basic.
i've been using both programs for years now, and OO is far from perfect - but i prefer it to ms office because it's easier to do the everyday things. it's just as stable in everyday use, i can use it anywhere, the UI doesn't change too much across versions, the formats don't change across versions, I don't have to pay to upgrade... i could go on. yes, it's slower - but we're talking fractions of a second for most operations, for god's sake. is it bigger? does anyone care these days, when hard drives are measured in the 100s of Gb? OO's saved documents tend to be smaller, in my experience - which is more important. i'm sure most people would be better off with ms office, but would they be [insert retail price here] better off? i doubt it.
in any case, the article spends 90% of it's words slating OO, then at the end the guy says he still thinks it's better for writing books. eh? he criticizes OO for having no support desk - is he serious!? how many MS Office users ring MS Support desk when they can't write in blue text? seriously. the article is full of this stuff - it's about as balanced as a one-legged trapeze artist.
OO has a way to go yet, but labelling it 'dire', and a complete failure, because it isn't as good (yet) as the dominant product in the sector, (which has had a monopoly for the best part of 10 years, and until recently was pretty buggy and resource hungry itself), is incredible. if it's so 'dire', why does he still use it himself?
Rights and wrongs (Score:5, Interesting)
What the Open Source community needs to take from Brown's article, and plenty of other critiques of Open Office, is that it's time to stop holding up Open Office as a shining success story. Pick something better, like Firefox, or the ability of BSD to adapt to everything from DVD players to cars to OS X.
not a good example (Score:3, Informative)
File under FUD (Score:3, Informative)
OpenSource alternative? (Score:3, Informative)
Brown quotes Ou on OOo2 (Score:5, Interesting)
Like many of Ou's comparions, he loads the deck. For example, Ou claims FireFox has as many bugs and security holes as IE6 and even gives the nod to IE6. What he doesn't say is that his data is flawed. While FireFox is developed in full view of the public, with the users contributing to and able to browse the bug database, the users of IE6, including Ou, are kept in the dark about IE6 security holes until Microsoft decides to patch and announce them. So, while he reports ALL the FireFox bugs, he can only report the IE6 bugs that Microsoft allows to be made public, which exprience has shown is much lower in number than the actual IE6 bugs and holes. Ou's conclusion: FireFox has as many bugs and holes as IE6.
The Excel vs Calc comparison was just as loaded, just as slanted and just as impractical. It goes without saying that NO ONE in the real world uses a spreadsheet the way Ou used it, contrary to his claim. IN fact, Ou's spreadsheet was both impractical and worthless. The 'test' was merely a test of load times, comparing Excel with OOo2's Calc. The Excel file was in Excel's format as a 16 sheet spreadsheet with 32K rows per sheet, each row having 13 text fields with a total length of about 128 characters, IIRC. Why didn't Ou post his ODT file as an ODT file for OOo2? Why did he have to convert it to an SXW format to force those who would test his work to reconvert it back to the ODT format? The real question is, why was Ou using a spreadsheet when a database was called for. Ou reported that Excel loaded its Excel spreadsheet in 38 seconds and Calc loaded its ODT spreadsheet in 141 seconds. I don't own Excel but I did download his SXW spreadsheet, converted it to ODT and timed how long it took to load it. I, too, got around 140 seconds load time.
However, as a programmer I want to use the right tool for the job, and playing with 500,000 rows of text data isn't a job for a spreadsheet, it is a job for a database. So, using OOo 2.0's database capabilities I converted the ODT spreadsheet into a database. That took only a minute or so. Testing the load time as a database I found it to take less than ONE SECOND!!. Then I let OOo 2.0 automatically create a form, using its form autopilot, with which I could view, search, navigate, add, edit or delete the data. That also took less than a minute to do.
Then, I thought about timing how long it would take Excel to do those things I did with OOo 2.0, but I discovered that Excel doesn't have a database, it doesn't have a form autopilot, so the time it would take to do those things would be infinite. So, by Ou's logic, OOo 2.0 is infinitely faster than Excel.
Browns other criticisms can be as easily dismissed. By relying on Ou's slanted work to prop up his smear of OOo, Open Source and the Baazar, Brown has unmasked himself as a Microsoft shill of the worst kind... Mimiking the wolf who wore grandma's clothing in his attempt to kill Little Red Riding Hood, Brown is trying to kill FOOS while wearing a Penquin suit.
same reason office 97 was a success (Score:4, Insightful)
Office 97 was a buggy pile of shit too, but heaps of people still use it and refuse to upgrade (or are bound to it by Access97 apps they refuse to rewrite/pay to rewrite), because it's "good enough".
smash.
I dunno, it works for me... (Score:3, Interesting)
I impressed my district and regional managers with a few spreadsheets and documents I put out with OO.org (2.0), and showed 'em what happens when they give productive people useful tools.
I count Open Office (at least, version 2, which is LIGHTYEARS in usability ahead of 1) as a very useful tool.
Brown is confused (Score:4, Insightful)
Is Microsoft Office faster and smaller than OpenOffice? Perhaps, but that's really not relevant. Office suites aren't in a pissing contest for speed or size. Software engineering involves a lot of tradeoffs and making an office suite faster than it needs to be is a waste of time and poor engineering practice. Also, OpenOffice solves a harder problem: it needs a cross-platform codebase (Microsoft just develops largely separate versions) and it needs to maintain compatibility with Microsoft Office.
Now, who is responsible for what OpenOffice is? OpenOffice was originally developed as a closed source piece of software. Much of the code is still that original code. Many of the decisions that are causing problems are still the decisions made back then. And development continues with developers supported by big companies. So, it is wrong to place the blame for OpenOffice's problems on open source. I think overall, open source has greatly contributed to OpenOffice and OpenOffice would be dead by now if it had remained closed source. On the other hand, without the initial proprietary effort, OpenOffice almost certainly wouldn't be as mature as it is.
Brown has some kind of bizarre model of open source in mind where it's only open source if a large portion of individual users contribute. But that's wrong. Open source is a licensing model that ensures access to source code, nothing more and nothing less, and OpenOffice fulfills that. Furthermore, in the case of an office suite, the "users" are big companies: when IBM wants to ship OpenOffice, IBM is the user, and IBM contributes (they happen to do so with software, donations and developers). And it is not necessary, and has never been the case, that a larger percentage of the user base contribute; a big user base is useful for an open source project even if most of the users are not developers. Finally, open source development has never been hugely efficient: open source projects usually take much longer to complete in real time than comparable proprietary projects; but that has never been a problem, and I don't see why it should be a problem now.
Overall, Brown is just confused: about software development, about engineering, and about open source. Maybe Brown should stick to commenting about things he knows something about.
(As for Brown's "most irritating bugs", I would classify them as WONT-FIX and NOT-A-BUG. If those are the biggest problems he has with OpenOffice, then OpenOffice is doing well.)
As a potential contributor... (Score:4, Insightful)
In spite of all that, Brown still admits that OO is better for writing books than Word, and that Word 97 couldn't even print a 60k word manuscript... I'd imagine word 03 can do that, but I don't know. I use OO every day for everything, I haven't noticed a single "bug" in OO 2.0 that makes the software unusable. I use it for Invoicing, Code documentation, User documentation, creating pdf's of everything I write basically, project planning, opening word documents and excel spreadsheets, everything. I don't even have MS office installed on a single machine I use anymore (more than 20 machines). Does OO open slower than MS Office? Yeah a little... maybe 5 seconds... so what? Have I ever had it crash and lose a 50 page user manual? No not once! Has that happend with MS Office? Used to be a regular occurance!
The OO community process could use some work, its hard to contribute to the project, but, at the same time, for a free office suite, it works exceptionally well for me.
OpenOffice isn't exactly open source. (Score:3, Informative)
For an Open Source product to have thriving success, it needs to be BORN open. Take firefox, for example. Even when Netscape opened its source, it had to be rewritten from scratch to fix most of the rendering bugs (massively nested tables, anyone?).
In other words, a definition I would like of Open Source Software is that it's created bottom-up. The author plants a then other people come and make it grow.
Having ONLY ONE AUTHOR would be the same as a closed-source product. What use is having the sourcecode available if nobody reads and modifies it?
Also, the program must be well-designed by its original author. Writing a program with a buggy and limited infrastructure will need to be refactored sooner or later. Multi-tier design (even in non-database apps) is a requisite.
So, if one open source program isn't designed to be configurable (hardwired values, non-unicode strings in wxWidgets), extensible (no support for modularization), it will be very difficult to overcome its limitations.
The Open Source isn't a panacea. It's a field where programs evolve (like genetic algorithms). Good programs survive, bad programs get often forgotten.
But Open Source itself does NOT guarantee a program to be bug-free. It just facilitates the conditions so the bugs can be fixed soon.
So if OpenOffice has serious bugs, don't blame the Open Source model. And yes, I don't like OpenOffice very much, as a longtime MS user, I find some of the interfaces kinda "alien" (but I manage to survive without MS Office installed, and that's a very good thing), and to my frustration i had tried OpenOffice when it still was version 1 (about 5 years ago). eew. >_<
Re:Only problem (Score:3, Interesting)
So, like other FOSS apps, there may be many eyes on it, but they probably never even look at the source, let alone work on it. It's too big and complicated. And people are already being paid to work on it. Why should someone spend their free, spare time doing someone else's job?
It may be open source but I suspect that it's development hasn't been a very open process. This is just about the worst example in the FOSS world to use as a repr
Re:Only problem (Score:3, Interesting)
The number of bugs or contributors is really irrelevant and the article is wrong here. If SUN wants to encourage OO development, they shall organise at least 10 developer meetings per year. One in Hamburg, one Fosdem session, etc. etc. Infor
Re:Open source is a joke (Score:3, Insightful)
Real software? You mean, like Real Player? No loosely assembled code lines for sure.
Do you think a bunch of hippies would do something useful, apart smoking their pot.
At least I'm doing something useful right now! Thanks for the support, I'll keep up the good wo.. err.. smokin'
No, they write software that is outmoded since 1983, and call thelm "free".
Mhh, there'
And let us not forget... (Score:5, Insightful)
It's also dead easy to take multiple OO Impress presentations and splice them together into one big presentation. However, try doing it in Office. Again, how to do that is not obvious at all, and it should be.
There's also something I brought up in another thread here: Open Office will fix corrupted and virus-laden Office documents. Just save in Open Office native format, then resave the OO.O native file as
OO.O rocks. I want to see a version that will natively run under OS X, but as long as iWork exists, Apple's not going to encourage it. OK, no problem, I'll run it happily under Linux.
Re:And let us not forget... (Score:3, Interesting)
To me, assuming OO were sped up, and it retained the same GUI, I cannot get used to it enough to be productive. I've found the menus too unintuitive to figure out. If they would kindly
Re:And let us not forget... (Score:3, Interesting)
Just to mention that Neo Office http://www.neooffice.org/ [neooffice.org] was born due to no native version available under OS X. Its only available in a 1.x source tree due to the massive undertaking required to get it work.
I wish Sun would do a better job and make it run natively under OS X, get rid of those static assigned libraries (.dll /
Also some beautiful / appealing templates in Oo such as those which are available in Apple's Pages would be fabulous.
I run Office u