LWN: Comments on "Meeks: A LibreOffice/Apache OpenOffice Comparison" https://lwn.net/Articles/494686/ This is a special feed containing comments posted to the individual LWN article titled "Meeks: A LibreOffice/Apache OpenOffice Comparison". en-us Wed, 12 Nov 2025 01:13:04 +0000 Wed, 12 Nov 2025 01:13:04 +0000 https://www.rssboard.org/rss-specification lwn@lwn.net OO development processes mean everything https://lwn.net/Articles/495951/ https://lwn.net/Articles/495951/ cesarb <div class="FormattedComment"> <font class="QuotedText">&gt; I didn't realise until I read your comment for the third time is that the way you think and react is exactly what is wrong with the OO, but not the LO culture ... your culture is one in which code bases need to be PROPERLY maintained and needed new features come from the Marketing Department, which the get by talking to self selected senior users.</font><br> <p> What.<br> <p> I completely fail to understand how you could get *that* from my comment.<br> </div> Fri, 04 May 2012 12:41:33 +0000 OO development processes mean everything https://lwn.net/Articles/495918/ https://lwn.net/Articles/495918/ brianomahoney <div class="FormattedComment"> I didn't realise until I read your comment for the third time is that the way you think and react is exactly what is wrong with the OO, but not the LO culture ... your culture is one in which code bases need to be PROPERLY maintained and needed new features come from the Marketing Department, which the get by talking to self selected senior users.<br> <p> OO has been incubating for decades, always trying to catch up with MS Office.<br> <p> Bound to fail!<br> <p> LO has what any good software needs, a vibrant developer community that want to do GOOD, NEAT things and ARE, without waiting for some droid's permission.<br> </div> Thu, 03 May 2012 23:44:16 +0000 Meeks: A LibreOffice/Apache OpenOffice Comparison https://lwn.net/Articles/495914/ https://lwn.net/Articles/495914/ brianomahoney <div class="FormattedComment"> Mr Meeks can sometimes bang the drum a bit loudly, BUT he is right on the money, LO got the community (of developers) while Ellison was scampering to catch up with Oracle's latest stupidity. In retrospect SUN and Oracle should make good reinforceing bed fellows since they both could never stop their hubris from damaging their business plan, and remember both are heirs of DEC.<br> <p> The bottom line is that Oracle dosen't know to monetize SUN's intellectual property, unsurprising, neither did SUN.<br> <p> LO has got the free developers, and while Apache had, in the day they are now another non-agile organization with too many policies and rules and not enough coding. For years to come, LO will slowly pull away from OO as more people do stuff not talk about how 'to do/or not to do' stuff.<br> <p> Go back and reread the Cathedral and the Bizzar.<br> <p> <p> </div> Thu, 03 May 2012 23:24:58 +0000 I always thought such a comparison would be just one single sentence? https://lwn.net/Articles/495759/ https://lwn.net/Articles/495759/ giggls <div class="FormattedComment"> Openoffice has got the brand, Libreoffice has got all the rest.<br> <p> No longer true anymore?<br> <p> Sven<br> </div> Thu, 03 May 2012 08:54:58 +0000 Linking to LibreOffice https://lwn.net/Articles/495521/ https://lwn.net/Articles/495521/ dmarti But a properly set up redirect would pass all or most of the link juice flowing in to go-oo. Tue, 01 May 2012 18:55:57 +0000 Linking to LibreOffice https://lwn.net/Articles/495462/ https://lwn.net/Articles/495462/ JanC_ <div class="FormattedComment"> Actually, it would help a lot if the Go-OO site stays there and keeps linking to LibreOffice. A HTTP-redirect doesn't show up in search results...<br> </div> Tue, 01 May 2012 16:10:06 +0000 Linking to LibreOffice https://lwn.net/Articles/495357/ https://lwn.net/Articles/495357/ dmarti <div class="FormattedComment"> That "new OpenOffice" link in your comment is basically the right idea. If enough people put links to libreoffice.org on high-ranking sites, the problem will go away.<br> <p> The go-oo site says, "Going forward, the Go-oo project will be discontinued in favor of LibreOffice," so if they put in the appropriate HTTP Redirect that should help a lot, too.<br> </div> Mon, 30 Apr 2012 23:41:37 +0000 That's not strict, that's rigid https://lwn.net/Articles/495082/ https://lwn.net/Articles/495082/ coriordan <div class="FormattedComment"> <font class="QuotedText">&gt; They are very strict</font><br> <p> Sounds more rigid than strict.<br> <p> If a policy blocks the goal, the policy should be discussed. (That's assuming that the goal of AOO is to improve the free software options available to users of office suites.)<br> <p> Take RMS for example. No one doubts that software freedom is his goal. He has policies about using GNU licences and GNU contributors assigning copyright, but in limited circumstances he recommends non-GNU licences and accepts code into GNU packages without copyright assignments. He puts the goal ahead of rigidly following policy.<br> <p> Before AOO, there was little worry about the motivations within the Apache project. But there are also no illusions about the motivations of Oracle Corp and IBM. Each has a lot of influence in AOO. If a decision is bad for software freedom but good for Oracle or IBM, and the decision is supported by rigidly following a policy, then "we're really strict" can be a convenient fig leaf.<br> <p> </div> Sat, 28 Apr 2012 20:15:08 +0000 Few really new features in AOO (incubating) means nothing https://lwn.net/Articles/495070/ https://lwn.net/Articles/495070/ drag <div class="FormattedComment"> <font class="QuotedText">&gt; That policy is no fault of AOO; as far as I have heard, it has been Apache policy for a long time.</font><br> <p> Yes: This is a not a unusual issue that crops up with all Apache projects. They are very strict on the licenses they are willing to accept or re-license to.<br> <p> <font class="QuotedText">&gt; If we were trying to place blame, the fault would lie with the ones who chose to drop the giant ball of code in Apache's lap, knowing fully that it would mean creating a need to purge parts of that code.</font><br> <p> This seems like a inappropriate project for Apache to take on, then. Just because the ball was thrown at them doesn't mean that they are obligated to run with it. Maybe the devs on the Apache project would better serve themselves by placing their contributions under the auspices of the Libre project. <br> </div> Sat, 28 Apr 2012 15:25:48 +0000 Few really new features in AOO (incubating) means nothing https://lwn.net/Articles/494811/ https://lwn.net/Articles/494811/ cesarb <div class="FormattedComment"> <font class="QuotedText">&gt; That argument would carry more weight if AOO didn't bring that pain on themselves via the Apache licensing policy of refusing to use GPLed/LGPLed components.</font><br> <p> That policy is no fault of AOO; as far as I have heard, it has been Apache policy for a long time.<br> <p> If we were trying to place blame, the fault would lie with the ones who chose to drop the giant ball of code in Apache's lap, knowing fully that it would mean creating a need to purge parts of that code.<br> <p> The Apache OpenOffice (incubating) community had no choice in this matter, since it did not exist yet (it obviously started existing only after the code was thrown to Apache). They have to do their best with the preexisting situation: the strict Apache policy, the inherited bundle of code and artifacts with their licenses and grants, and the resulting intersection.<br> <p> IMHO, their best code of action (if they decide to go on separately instead of merging with LO) would be to release a clean working 3.4 as a base as soon as possible, and go on from there. From what I have seen, this is the course of action they are following.<br> </div> Thu, 26 Apr 2012 23:00:59 +0000 Few really new features in AOO (incubating) means nothing https://lwn.net/Articles/494804/ https://lwn.net/Articles/494804/ josh <div class="FormattedComment"> That argument would carry more weight if AOO didn't bring that pain on themselves via the Apache licensing policy of refusing to use GPLed/LGPLed components.<br> </div> Thu, 26 Apr 2012 21:59:36 +0000 Meeks: A LibreOffice/Apache OpenOffice Comparison https://lwn.net/Articles/494779/ https://lwn.net/Articles/494779/ gioele <blockquote>If this could be changed to top-5 of the first page it would go a long way towards solving this problem.</blockquote> <p>For some reason go-oo.org is on the first page of results for "openoffice". Couldn't that become an HTTP 301 redirect to the <a href="http://libreoffice.org">new OpenOffice</a> or host a big banner linked to LibreOffice above the fold?</p> Thu, 26 Apr 2012 20:08:27 +0000 Meeks: A LibreOffice/Apache OpenOffice Comparison https://lwn.net/Articles/494734/ https://lwn.net/Articles/494734/ sorpigal Searching for <a href="http://www.libreoffice.org/">OpenOffice</a> gets me a LibreOffice link... at the bottom of the second page of results. If this could be changed to top-5 of the first page it would go a long way towards solving this problem. Thu, 26 Apr 2012 17:34:02 +0000 Meeks: A LibreOffice/Apache OpenOffice Comparison https://lwn.net/Articles/494720/ https://lwn.net/Articles/494720/ jpnp <blockquote>One of the most curious things about the OpenOffice.org brand, is the loyalty that users have to it, despite the 3.3 feature freeze being twenty-two months ago, having lost much of it's development community, and having had no new release since January 2011 - users are still downloading this increasingly old and creaky release at top speed. <b>Getting the LibreOffice message out</b>: about the new, exciting, much more featureful, and fun suite is important - and much appreciated. Existing profoundly clueful GNU/Linux communities already know about the best free office suite ever others don't yet.</blockquote> I think this paragraph explains the rational for these type of articles. The OpenOffice brand had a pretty wide reach. There are many many people who search for OpenOffice and hit the download link without realising there is an alternative. I know I regularly meet people who've not even heard of Linux, but who use OpenOffice as a free alternative to MS Office on their windows boxes. Thu, 26 Apr 2012 17:12:58 +0000 Meeks: A LibreOffice/Apache OpenOffice Comparison https://lwn.net/Articles/494699/ https://lwn.net/Articles/494699/ and <div class="FormattedComment"> I don't know what to think about such comparisons. Whenever the LO people publish something like that I always have the impression that they are beating a dead horse...<br> </div> Thu, 26 Apr 2012 15:10:46 +0000 Few really new features in AOO (incubating) means nothing https://lwn.net/Articles/494687/ https://lwn.net/Articles/494687/ cesarb <div class="FormattedComment"> Having few new features (or even no new feature at all) in 3.4 would be expected, and in fact it is a good thing. They need a "baseline" release to base their work on, and need it fast (the longer they wait, the greater the chance of a critical security bug in 3.3 they cannot distribute a fix to). So their focus would be in releasing 3.4 as soon as possible, and not in adding new features to it (or even fixing bugs and cleaning up the code).<br> <p> A real comparison will be possible only with the next major release following AOO 3.4 (be it 3.5 or 4.0).<br> </div> Thu, 26 Apr 2012 14:01:58 +0000