Slashdot Mirror
Open Office Plans To Party Like It's Version 3.0
penguin_dance writes "The Register reports that 'OpenOffice.org is throwing a launch party in Paris on 13 October' to celebrate eight years, and hopefully announce the release of version 3.0. Some notes: [OpenOffice.org 3.0] will support the OpenDocument Format 1.2 standard, and be able to open files created by MS Office 2007 and Office 2008 for Mac OS X." As maj_id10t notes, though the OO.o site does not yet carry an announcement, "Lifehacker has posted an entry stating the final release of OpenOffice 3.0 is available for download via their distribution mirrors."
Like any other piece of software, there are things you feel like you couldn't live without and things you have to get used to. I remember it felt clunky when I first started using it, but that went away very quickly. Some things are more elegant than in MSOffice, some less. I've been using v3.0 for a while now (beta and fc releases), and I like it quite a bit. One of the big clunkinesses, the graphical depiction of comments/notes, is now very nice. There are still some screen rendering oddities that don't get in my way but do contribute to the impression of clunkiness. On the whole, I imagine it's still clunkier than its commercial counterpart, but the gap is narrowing. However, I rarely edit documents that are more than a few hundred pages long, and I know many of OO's critics say that its shortcomings are especially obvious if you work on long documents. So I can't comment on that.
How has MSOffice come along in the same time? Is pdf writing integrated now? Do files still bloat to ridiculous sizes on repeated editing?
OK, i just popped open OO.org to verfy your claims. here's what i found:
unless you're just trolling, you might make a more convincing case if you actually listed specific complaints instead of, oh i dunno, pulling things out of your ass? honestly, there are a lot of things to get used to when switching from MS Office to OO.org (i spent most of my life using MS Office), and that transition can be pretty frustrating. but don't blame your own inability to adapt (or to even try to adapt) on the software.
neither MS Office, nor OO.org are perfect. personally, i've had problems with both of them. but so far i haven't heard a single legitimate complaint leveled against OO.org. so i have to conclude that these groundless criticisms are just knee-jerk reactions to having to adapt to a new office suite application.
the only problem i've had to OO.org is trying to make PDF documents with complex layouts using tables with varying column/row spans. but i've had the exact same problem in Word. all WYSIWYG editors have quirks like these, and i can't say that one is better than the other.
Look at issue 43029.
Notice that it is classified as a feature request rather than a bug and its target milestone is only 3.2, despite being first created more than three years ago, having over 200 votes, and numerous comments on this issue and its various duplicates showing how it's a complete showstopper for using most professional grade fonts with PDF export.
This bug has become the standard counter-example in on-line discussions to all the OSS advocacy that claims many eyes make all bugs shallow, products will naturally develop according to users' needs because people can contribute their own patches, etc.
If you disagree, post your argument. (-1, Overrated) isn't your personal censorship tool for views you don't like.
I've come to a conclusion about those who say "write a patch" if you say there's a problem with something. Either they truly don't understand just how powerfully it turns people off from using their software, or they do know and it's an intentional "fuck you" to those they decide are "outsiders."
Either way, the outcome is the same: They actively drive users away, in FOSS's case back into the comforting arms of Microsoft. It creates a rift between reality and the developer's perception of reality, which results in the project not moving towards progress but orthogonally to it, or worse away.
And here enlies the problem with the "write a patch" types: I gaurantee you I can find an aspect of your computer you aren't an expert at, and you'd be pissed at me if I threw it in your face when you asked for help. Your accountant doesn't tell you to fix your own damn tax problem, the mechanic doesn't derisively laugh because you don't know how to re-gap your own spark plugs, and as a user of FOSS I'd prefer not being snidely mocked just because I don't dedicate hours a day learning your little corner of it. For all the egalitarianism of FOSS, there is still fundamentally a business relationship between the programmers and the users. Until we learn that and put a lid on the "write your own patch" people, it will never equal proprietary software except for a handful of diamonds in the rough.
Why so thorny? Because I've been a recipient of that attitude a few times. And not even my hardcore nerd's reverse tact filter could stop it from getting under my skin.
While I agree that the grandparent is engaged in some first-rate asshattery, I'd just like to make one comment. You say:
Your accountant doesn't tell you to fix your own damn tax problem, the mechanic doesn't derisively laugh because you don't know how to re-gap your own spark plugs
The difference here is that you are paying your accountant and your mechanic for their expertise. Most of the people who receive comments along the lines of 'write a patch' have not contributed anything. On the Free Software project I co-run, we have a designer on the core team. He provides a lot of really high-quality artwork and some good UI ideas. If he comes to me with a feature request, then it goes quite high on my TODO list. Why? Because he's contributed to the project in ways that I am incapable of replacing with my own effort. I recently refactored a big chunk of my code to make it more reusable for someone else. Why? Because at the same time as asking me to, he sent me a diff fixing a few of my bugs.
Free Software is about cooperation. I only benefit from sharing my improvements if other people do as well. We both benefit from not having to reproduce the other's work, and so can get on with things we want to do much faster. If you want something done, then you have to convince me that it's in my interest to do it for you, usually by offering something in return. Whether this is code, artwork, documentation, or money is up to you. If you don't offer anything then the reply will be 'patches welcome' which means either offer me something of value in exchange for my time, or offer someone else something and get them to send me the patch.
I am TheRaven on Soylent News