Live data from Hacker News

Contemplating the possible retirement of Apache OpenOffice

lwn.net

191–200 of 327 posts

Re: Contemplating the possible retirement of Apache OpenOffice

#191

Earlier quoted context omitted.

There's effectively a one-way merge already. LO can - and do - consume patches contributed to AOO. But, for a variety of reasons, that are mostly historical as far as I can tell, the LO developers have generally been unwilling to contribute code in the other direction. An outright "merger" of the two projects seems unlikely due to the licensing differences and the associated thinking. Some people prefer permissive li…

As I pointed out in the mailing list, there has been practically no development on OO this year though.

As I pointed out in the mailing list, there has been practically no development on OO this year though.

And? I mean, yeah, it would be nice to have more cool new stuff coming out, but it's not like AOO owes the world anything. It's open source, it's volunteer driven. If people want more new features, more development, etc, then more people need to volunteer. If they don't, well... the world gets what it gets from the folks who are contributing.

Re: Contemplating the possible retirement of Apache OpenOffice

#193

Well, my prediction[1] came true even faster than I anticipated. I don't understand why so many people seem so desperate to see AOO fail and go away. Hey look, if you prefer LO, fine. Some of us prefer AOO for our own reasons. There's no reason to take glee in seeing a project struggle. Anyway, none of this means the project is actually going to be retired. It's just a discussion around something that might happen. […

> I don't understand why so many people seem so desperate to see AOO fail and go away. In my case, the reason is splash-damage from the inverse-goodwill I have for Oracle and how their stewardship of OO (or lack thereof). To start off Sun handled the OOO-patchset (proto-LibreOffice) poorly, they should have merged it to mainline. Then Oracle came along and shat on the community leading to an outright fork. This I gue…

At the time, it was not clear what the outcome of the community split was going to be. But what tipped the scales was getting the assets out of Oracle.

Even if the nascent project had only managed to receive the code and make one release before folding, that was worthwhile enough to justify accepting the donation. The project managed to flourish for some time after that, so in that regard it was well above baseline.

Re: Contemplating the possible retirement of Apache OpenOffice

#194

Have OpenOffice actually done anything.

This image would suggest it got some code from StarOffice and alter some releases: https://upload.wikimedia.org/wikipedia/commons/thumb/f/fb/St...

Well, here it looks like Apache OpenOffice made a couple of releases.

Re: Contemplating the possible retirement of Apache OpenOffice

#195
post #82

Earlier quoted context omitted.

It was immediately obvious at the time, I remember it as such. The devs jumped ship to LibreOffice. All Oracle was left with was a brand and a moribund codebase, and for some reason Apache accepted it. Why didn't Oracle give it to LibreOffice? Because they were sore at being bypassed, it looked like. The correct thing for Apache to do would have been to say, nope mate, we don't want to be part of your childish feud,…

If Apache had not accepted it, Oracle was NOT going to donate it to TDF. Instead, Oracle would simply have shuttered it, or sold it to IBM. There was no workable plan ever that would have resulted in the OO code going to TDF. Even if AOO had never done a single release, LO still benefited enormously from OO going to Apache, since once at Apache, there was known and public IP provenance, AND the code was relicensed to…

The Apache Foundation could simply have accepted the OpenOffice.org codebase+trademarks from Oracle, then donate to LibreOffice.

But they did not do so. The Apache Foundation does not have experience with software that end-users use. They have experience with server software. That was their undoing.

Re: Contemplating the possible retirement of Apache OpenOffice

#196

Earlier quoted context omitted.

I speak en-AU - I'm not sure what connotations "libre" has to most English speakers who haven't learned a Romance language or been involved in the Free Software world. "Libre" is not a common English word - I imagine to many English speakers you'd probably have to explain the shared etymology with "liberty" for people to get it. The French pronunciation is non-obvious to an English speaker.

"Liberty Office" would have been a much better English moniker.

Uggh... it sounds horrible ! Makes me think of the statue of liberty and US flags..

Re: Contemplating the possible retirement of Apache OpenOffice

#197
post #182

Earlier quoted context omitted.

My experience would be the contrary. I felt Libre Office had better document compatibility and a better user experience, so I stopped using Open Office. Maybe it improved since then. I would also like to see something to back up the claim you are talking about.

In my personal experience, when I first tried Open Office it ended up being a clunky, unreliable clone of older Microsoft Office products. It was still better than a kick in the teeth though. In all honesty, after writing my own simple manual editor for PDF, I really don't envy the task of making something compatible with multiple other formats. It would be nice to see the project archived or completely released to t…

> ... clunky, unreliable clone of older Microsoft Office products. It was still better than a kick in the teeth though.

That's exactly why i am using Open/Libre office; at some point Microsoft Office got such a complicate UI (ever since they pushed the ribbon bar - that's when they kicked me in the teeth) that i am unable to use it - the alternative uses a much less complicated UI so i am with it. Does the MS Office UI conform with the Windows UI guidelines ? I am not quite sure..

As for 'unreliable' - i can't share this perspective; LibreOffice works for me; didn't have any problems with OpenOffice either - before i switched to LibreOffice. I switched because LibreOffice is supposed to have better support.

Interesting that MS often gets to a point where the UI is quite adequate, but then they have to come up with something new, so they come out with an update that breaks it all. Happened with Windows, Office, Visual Studio, Visual Basic - you name it; i think it also happened with gmail - so it does not seem to be something exclusive to MS; i wonder if that is a general law of software development.

Re: Contemplating the possible retirement of Apache OpenOffice

#199
post #188

Earlier quoted context omitted.

French is the worst thing to happen to language. What's that open Nvidia driver called? Novou? Neauveau? Nouveau? Neauvou? Fuck it.

English is way worse than French. It's just that more people are used to it.

English is crummy because of French :P

Re: Contemplating the possible retirement of Apache OpenOffice

#200
post #74

Earlier quoted context omitted.

I agree in the case of the Windows/OS X environment, where brand awareness of LibreOffice is low, but in the Linux world... my distribution (Debian) doesn't even package OpenOffice, and I don't know any Linux user who uses OOo.

Here's one. Never thought it necessary to change. OO works just fine.

LibreOffice is original OO, in terms of continuity of development, more so than AOO is.
Post reply on HN