LibreOffice 3.3 Released Today
mikejuk writes "Only four months after the formation of the Document Foundation by leading members of the OpenOffice.org community, it has launched LibreOffice 3.3, the first stable release of its alternative Open Source personal productivity suite for Windows, Macintosh and Linux. Since the fork was announced at the end of September the number of developers 'hacking' LibreOffice has gone from fewer than twenty to well over one hundred, allowing the Document Foundation to make its first release ahead of schedule The split of a large open source office suite comes at a time when it isn't even clear if there is a long term future for office suites at all. What is more puzzling is what the existence of two camps creating such huge codebases for a fundamental application type says about the whole state of open source development at this time. It clearly isn't the idealistic world it tries to present itself as."
I'm pretty sure that we'll be stuck with Office suite for a long long time still...
But saying that this unmasks Linux as not being perfect is like saying your family is not perfect because you brought your kid to the hospital after he was hit by a car instead of hiding the fact...
A fork in this case is a wonderful solution to a death by stagnation caused by proprietary idiocy from Oracle.
link to main site http://www.libreoffice.org/ instead of lame-ass blog talking about it
I tried it today for the first time and I must say, I am impressed :)
The UI seems much better than the last time I used OpenOffice (maybe v2) and the graphics seem to have been created by professional designers, as opposed to the developers themselves. I had a DOC that was crashing my Word 2007 and I got it opened with ...LibreOffice. Probably has to do with Microsoft not even keeping up with their own standards (and I'm honestly not trolling).
Now that they don't have to worry so much about maintaining compatibility with Sun/Oracle's version (like they did with the go-oo fork), they can fix a lot of old cruft. If you want to get involved, there is a list of easy hacks that should provide a starting point for people who want to contribute.
http://wiki.documentfoundation.org/Development/Easy_Hacks
http://blindscribblings.com - Tasty pop-culture in conceptual fashion.
The fork is good news, the new stable released is better news and the hundreds of devs is great news. Why is the OP insisting to put a negative spin on this?
I find LibreOffice much more usable than OpenOffice.org on the Mac, but it still not to the point of reliable. Especially when it comes to mouse clicks.
I have also found that when I file a bug report on OpenOffice.org I get a response to clarify the bug or reject my bug, but with LibreOffice, I feel like my bug just sits there unread.
Oh, well perhaps they will get better in the future. At the LibreOffice community is will to make patches that improve the package, OO.org seems to reject any Mac based usability improvement patches, so NeoOffice was formed (but has been stuck at version 3.1 forever)
Somehow, the news that LibreOffice is right on track is spun into a negative diatribe against FOSS. We should be happy that we dodged a bullet and ditched an Oracle-controlled project. As well, this is another piece of proof that a major project can be forked without too much trouble. To me, this is nothing but positive, yet it's been spun into something else.
Yet Another Tech Blog
(but so much more, including game and movie reviews)
http://yanteb.peasantoid.org
Free Open Office. Then you guys can release a "Ribbon" like MS did, only you can call it the "Bar". That way we can discuss about things the "FOO Bar" can do.
Orwell was an optimist.
I can't believe that the name LibreOffice stuck.
I'm a native spanish speaker, and it sounds so goddam awful. Specially when mispronounced by pretty much everyone.
I know this is a personal opinion, but still.
"What is more puzzling is what the existence of two camps creating such huge codebases for a fundamental application type says about the whole state of open source development at this time. It clearly isn't the idealistic world it tries to present itself as."
How bloody clueless. This is like questioning the fact that we have more than one set of automobile designs and assembly plants, or more than one political party, or multiple soft drink bottling and distribution networks.
http://alternatives.rzero.com/
I'm not sure what Oracle's intent was with OpenOffice, but their actions sure caused a lot of very good people to leave in a hurry. Between this and the Android situation, it seems like Oracle really doesn't get free software, or worse, sees free software as the enemy. I'm not sure which. Regardless, I'm thankful that I get to use OpenOffice and now LibreOffice.
-- $G
It doesn't even have to be a company scooping up a project and destroying it. It could be a non-profit organization such as XFree86 that had allowed a system to stagnate.
The real advantage of easy forks is that it prevents organizational issues from standing in the way of technological progress. If the fork is significantly better than what it had forked, it will get developers and usage and become dominant. If it's not, it will die, the main trunk will live on, and many valuable lessons are learned. Either way, the users win.
I am officially gone from
So, what are the differences between OO.o and LibreOffice?
I've read the new features page. Are there any OpenOffice.org features or bug fixes that won't be included in LibreOffice? Does Oracle still have anything useful to offer or is OO.o effectively obsolete?
Sure - it makes sense; finally it is fun to work on LibreOffice - I for one, am enjoying seeing my work actually get included, and become useful to people without lots of dumb paperwork, and Oracle control-freakery.
If the first two were their goal, this release means that for all intents and purposes they have failed. If the third was their goal, they have succeeded; OO.o is dead. If they wanted to kill it to get rid of a successful OSS office suite that is a failure. However, if they wanted to kill it because they didn't want to be running an OSS Office sute project, then they got what they wanted.
The truth is that all men having power ought to be mistrusted. James Madison
I believe Java has matured enough under Sun to not be as vulnerable as some of the much younger languages. To be honest, I haven't seen any instance where Oracle is mortally screwing up the language.
If your thinking about the Oracle v. Google lawsuit, I'm siding with Oracle on that one. As much as I like to side with Google, the fact that they did the equivalent of ROT13 to the bytecode generated by the javac makes it hard to ignore what Google was doing. It would have been different if Google attempted to get a license to make there own mobile JVM or used the code from the OpenJDK base and challenged Oracle in court on the definition of a phone during 90's versus the much powerful mini-tablets of today. That didn't happen. Instead Google got caught doing what everybody thought was a poor attempt to hide the fact that Java is the basis for the Android OS.
These comments are my own and do not necessarily reflect the views or opinions of my employer or colleagues...
Just as I was getting senior staff comfortable with the idea of giving OpenOffice a try on some of our machines, this fork happened and someone brought in news of it. Now it doesn't matter that both can write to the same formats, and that you can have the programs save by default to MS formats. It introduced uncertainty, and many business leaders associate uncertainty with increased costs. Do you blame them? There's no confidence that a selected open source solution will provide a stable, long-term platform.
Now, I'm just happy I've been able to get some of our workstations moved over to FF. The entire open source movement has plenty of benefits, but those benefits are viewed as drawbacks by much of the traditional business community.
I use irony whenever I can, but my shirts are still wrinkled...
The logic applied here amuses me greatly but more so the Glenn Beck-ish puzzlement about what this says about open source:
It clearly isn't the idealistic world it tries to present itself as.
Define 'clearly' because having tons of options sounds really really awesome to me. You make it sound like everyone has to throw their lot in together or this effort is for naught. Everyone knows that isn't true. Secondly, who presents open source to be 'idealistic?' And how do you figure that people working on what they want equates to anything sub-optimal?
My work here is dung.
MS Word's doc-parser has been flaky for <drumroll>...decades</drumroll>.
Both I at my office (environmental modeling) and my wife (corporate legal) have had abiword and Openffice save the day many times when MSWord declared documents to be corrupt. Frankly, the opensource doc-parser library is much more robust than the one from Redmond. Do you know how much fun it is to be 8 hours from an NSF grant-deadline and have MSWord declare your proposal corrupt when yoo go to do the final printing? Abiword saved us that time -- way back in 1996! (and the situation hasn't improved much since.)
"My opinions are my own, and I've got *lots* of them!"
You should look into the Google case more. While the obvious stuff about Dalvik being a shameless rip of Java is true, it's not illegal, and the actual copyrighted code being sued over is not used in any way for a production Android system -- it's just the sort of testing cruft that builds up in a code repository if nobody's careful. Google's certainly liable for damages, but those damages will not be much, and the success of Android is in no way affected by any possible outcome.
Normally I'd agree with that. However, we're talking about opening a largely undocumented file format. MS office should be the gold standard in opening their own files. You save it in word, it should open in word - end of story. For any application to fail that test indicates a lack of something. The fact that people are often able to open their "corrupt" files using another tool indicates that part of the something missing is robustness.
How does rescuing an app from a company that was going to destroy bring uncertainty? If anything, LibreOffice provides certainty by showing that good opensource apps will always be around, despite efforts by some companies to harm them. If you're concerned about uncertainty in your core apps, I'd be much more concerned about the next "ribbon" that Microsoft will throw at you in a couple years than by the ability of open source app to maintain and improve itself despite the best efforts by others to ruin it.
If you're using Ubuntu, and want to try LibreOffice, I wrote a few details here:
http://www.fabianrodriguez.com/blog/2011/01/25/the-document-foundation-launches-libreoffice-3-3
Most importantly *don't install .debs manually* and *don't reinstall if you already have 3.3 RC4, it's the same as 3.3 final* :)
Notepad specialist & FAT administrator, group training available
Well, the JVM is as much the base of Android as it is the base of, say, Parrot or LLVM. Canonical Java is run on a stack-based virtual machine - the JVM - while Dalvik (and the other examples I mentioned) are register-based VMs. It is the virtual machine that matters here, not the language which itself is a member of the C family and stands on the shoulders of many giants.
And yes, if you wanted to get Java code to run on the Parrot VM you might want to use some of Java's own test routines to ascertain that you're doing it right. That would not mean you'd be calliung your implementation 'Java' of course, just that you implemented the capability to translate Java source code to (eventually) Parrot byte code.
In other words, I am not siding with Oracle on this one. As to the validity of the software patents referred to in this case I will just say that software patents are invalid where sanity prevails.
--frank[at]unternet.org
Normally I'd agree with that. However, we're talking about opening a largely undocumented file format. MS office should be the gold standard in opening their own files. You save it in word, it should open in word - end of story. For any application to fail that test indicates a lack of something. The fact that people are often able to open their "corrupt" files using another tool indicates that part of the something missing is robustness.
Yes, it should open in MS-Word if you saved it in word, every time, you are right. But you cannot conclude Abiword (or OO/LO) is more robust if you have one (or a few) examples where it was able to open a file and MS-Word wasn't. You only tried Abiword when MS failed, you didn't try Abiword everytime MS succeeded, and you might have found some Abiword failures then.
It sounds like Tio Paco is annoyed that we actually fight for things that matter. Idealism means that. It doesn't mean that you live in utopia, it means that you fight to improve things.
Bruce Perens.