Slashdot Mirror


Apache OpenOffice 4.0 Released With Major New Features

An anonymous reader writes "Still the most popular open source office suite, Apache OpenOffice 4 has been released, with many new enhancements and a new sidebar, based on IBM Symphony's implementation but with many improvements. The code still has comments in German but as long as real new features keep coming and can be shared with other office suites no one is complaining." The sidebar mentioned brings frequently used controls down and beside the actual area of a word-processing doc, say, which makes some sense given how wide many displays have become. This release comes with some major improvements to graphics handling, too; anti-aliasing makes for smoother bitmaps. In conjunction with this release, SourceForge (also under the Slashdot Media umbrella) has announced the launch of an extensions collection for OO. Extensions mean that Open Office can gain capabilities from outside contributors, rather than being wrapped up in large, all-or-nothing updates. You can download the latest version of Apache OpenOffice here.

56 of 238 comments (clear)

  1. IBM Open Source by Antony+T+Curtis · · Score: 2, Insightful

    For IBM, Open Source == Out Sourcing.
    Cheaper than employing programmers in faraway places is to get them to volunteer for free to maintain their code.

    Not new really... They have been doing that for years.

    --
    No sig. Move along - nothing to see here.
    1. Re:IBM Open Source by Anonymous Coward · · Score: 5, Informative

      I can't let bullshit like that stand.

      IBM specifically dedicates a group of developers to every project they open source, as far as I can tell.

      For OpenOffice, this is even mentioned in the Wikipedia article:

      The developer pool for the Apache project was seeded by IBM employees, who continue to do the majority of the development.

      And yes, I checked the references. The statement is correct.

      You are an asshole, for lying like that. BOOO!

    2. Re:IBM Open Source by dfghjk · · Score: 2

      The OP is correct and your two positions are not contradictory.

  2. German code comments by mwvdlee · · Score: 4, Insightful

    I'm a Dutchman, my native language is dutch, and I use english for all comments because using my native language seems to screw with the industry-standard english terminology in programming.
    Anybody here who comments his/her code in his native language? How do you deal with the jargon and what are the benefits of using your native language, apart from being able to type TL;DR-size comments with ease?

    --
    Slashdot social media options: AIM, ICQ, Yahoo, Jabber and Mobile Text. Why no MySpace?
    1. Re:German code comments by K.+S.+Kyosuke · · Score: 5, Funny

      I'm a Dutchman, my native language is dutch, and I use english for all comments because using my native language seems to screw with the industry-standard english terminology in programming.

      It also makes your programs faster. This is one of the reasons why OpenOffice is so slow - source. It's inexcusable that they haven't translated the comments yet.

      --
      Ezekiel 23:20
    2. Re:German code comments by slartibartfastatp · · Score: 4, Insightful

      My team code (variables, class and method names) and comment in portuguese. I found that not many programmers down here really know english, so our first attempts with english commentary yielded crappy, useless, unreadable comments. Even comments in our native language sometimes can be confusing, so I think that adding a extra layer of noise wouldn't do it.

      --
      -- --
    3. Re:German code comments by smittyoneeach · · Score: 2

      I think you meant it make people run faster from maintaining your programs. Unless your comments are in Klingon, in which case the would-be maintainer is vaporized.

      --
      Get thee glass eyes, and, like a scurvy politician, seem to see things thou dost not.--King Lear
    4. Re:German code comments by slartibartfastatp · · Score: 2

      7 years ago, when the project started, we were focusing on Latin America community (spanish speakers can read portuguese and vice versa), so I decided to code in portuguese. Only a few people from Brasil decided to contribute to the project since then, so I guess the language choice actually helped those contributors.

      Not that this choice doesn't look strange; we code in CakePHP, which is based on RoR, that specify that model names are plural, table names are singular, or whatever. We turn the pluralization off, as the english rules applied to portuguese words makes a mess. And writing a Inflector for portuguese really seems a huge work.

      Also, we are required to append suffixes in english to some classes names; we end up with classes named like "AmostraController", "ProjetoComponent". Which in fact is Ok, as here in Brasil we use english jargon. People from Portugal would think it's bizarre, I guess.

      --
      -- --
    5. Re:German code comments by Archangel+Michael · · Score: 4, Funny

      You have never experienced OpenOffice until you have used it in the original Klingon!

      --
      Agent K: A *person* is smart. People are dumb, stupid, panicky animals, and you know it.
    6. Re:German code comments by gaspyy · · Score: 2

      Romanian here. Everyone worth their salt here writes code, comments and docs in English. I have my own pet project where I'm basically the only one who ever needs to see the code, yet everything is in English. Considering that the programming language has English keywords (if, while, class, etc) and the text strings are in English too, it's simpler for me to keep everything consistent rather than to make any mental switch.

    7. Re:German code comments by Zontar+The+Mindless · · Score: 4, Informative

      Because the original codebase comes from StarOffice, which was developed by a German company (StarDivision).

      --
      Il n'y a pas de Planet B.
    8. Re:German code comments by K.+S.+Kyosuke · · Score: 2

      Except for commas. Note how a disproportionate amount of Germans write "Note, that..." instead of "Note that...". Interlanguage fossilization and all that jazz. Funny how you can often tell from an English text who actually wrote it.

      --
      Ezekiel 23:20
    9. Re:German code comments by kthreadd · · Score: 3, Funny

      That, is true.

    10. Re:German code comments by smittyoneeach · · Score: 2

      In Soviet Russia, Office Opens you!

      --
      Get thee glass eyes, and, like a scurvy politician, seem to see things thou dost not.--King Lear
  3. Play Nice by fermion · · Score: 5, Insightful
    Before we all start cat fighting, remember that 12 years ago Sun gave us a office application that competed well with MS. I have used it for all that time, and have been able to what I most of what I need to much better and reliably then with MS Office. I supplement it with Apple stuff and lately with Google Docs, which is not as good.

    Yes a few years ago some who did not like OO.org structure created an alternative which some prefer, and there is an issue with Oracle buying OO.org, but now Apache has it.

    So before we start modded up the MS shills who want to promote the OO.org versus Libreoffice battle, remember that OSS is about choice, and MS is about the destruction of choice.

    Thanks to all the people who have put work into OO.org. It is very appreciated. I have downloaded the new version and will look at it as I need it.

    --
    "She's a scientist and a lesbian. She's not going to let it slide." Orphan Black
    1. Re:Play Nice by Sique · · Score: 4, Informative

      Actually, the story is somewhat longer and started with Star Division, a Hamburg (Germany) based company, who offered a wordprocessor in the 1980ies for 150 DM in Germany, when the comparable Microsoft Word was about 800 DM or more. StarWriter was build into a whole office suite until 1995, when it got renamed in StarOffice. In 1999, Sun Microsystems bought Star Division, and in 2002 opened the code and created OpenOffice. Completed with some non-open licensed parts (like an RDBMS; if I remember correctly, StarOffice was using ADABAS from Software AG, later the derivate SAP DB), OpenOffice was sold as StarOffice by Sun Microsoft until 2010.

      --
      .sig: Sique *sigh*
    2. Re:Play Nice by Anonymous Coward · · Score: 5, Insightful

      You need something like Outlook

      Nonsense. Nobody ever needed Outlook. And nothing good ever came from Outlook.

    3. Re:Play Nice by ScottCooperDotNet · · Score: 4, Insightful

      You need something like Outlook

      Nonsense. Nobody ever needed Outlook. And nothing good ever came from Outlook.

      It freed us from Lotus Notes.

  4. Re:Merge Already! Libre/Open by kthreadd · · Score: 4, Informative

    Because they use different licenses. OpenOffice uses the Apache license, LibreOffice mostly GPL. Merging them is not feasible since either of them would have to give up something they don't want to in return.

  5. Re:Merge Already! Libre/Open by Anonymous Coward · · Score: 5, Interesting

    They are merging! LibreOffice imports all useful bits. They even keep a running commentary on any commits that are still going into apache office saying which are useful, which are not useful or which libreoffice commits fix something in a more elegant way: http://cgit.freedesktop.org/libreoffice/core/log/?h=aoo/trunk&showmsg=1

  6. And LibreOffice is already merging improvements by Anonymous Coward · · Score: 5, Informative

    LibreOffice 4.1 is out later this week and they already imported all the bug fixes from Apache Office. According to https://www.libreoffice.org/download/4-1-new-features-and-fixes/ they picked up at least these improvements:
    "A very large number of bugs have been fixed at an estimate of around 3000 bugs, of which 400 came from authors with apache.org mail addresses."
    and
    "Sidebar (Apache OpenOffice/IBM Symphony) with resizeable layout (LibreOffice team)"

    I wonder when apache office will merge fully with LibreOffice.

    1. Re:And LibreOffice is already merging improvements by luciano.moretti · · Score: 5, Interesting

      It won't. At this point the codebases have incompatible licensing. LibreOffice can continue to pull in code from OpenOffice, but OpenOffice cannot pull back in code from LibreOffice.

      As such, LibreOffice will likely continue to have major releases a week after OpenOffice, where all the good stuff from OpenOffice will get pulled in, but none of the good stuff from LibreOffice will be ported to OpenOffice.

    2. Re:And LibreOffice is already merging improvements by Palestrina · · Score: 4, Interesting

      Actually, this is not quite true. There are a good number of contributors who are happy to work with both projects. They don't care about the license bullshit. They contribute equally to both projects. So there is a fair amount of code making it back into AOO from LibreOffice.

      Also, some supports of free office software, like the Open Source Business Alliance (OSBA) which sponsored much of the OOXML improvements in LibreOffice, have put a clause in their contracts that requires the code produced to be made under the Apache License, even when the code is targeted to LibreOffice. So AOO will have access to that work as well.

      Of course, these are just small improvements to an overall climate of inefficiency. And the inefficiency goes in both directions. To the extent LO does not contribute patches upstream they are creating a deferred merge expense that will increase over time, each time they try to merge features down from AOO.

    3. Re:And LibreOffice is already merging improvements by asmkm22 · · Score: 2

      I wonder when LIbreOffice will finally merge back with OpenOffice. Especially considering how much they are just copy/pasting features and bug fixes. I still think the OpenOffice name has a hell of a lot more recognition than LibreOffice, which doesn't exactly roll off the tongue, and is only highlighting how difficult it can be for a business to switch to open source options when questions like "what's the difference between LibreOffice and OpenOffice" can't easily be answered for the people in charge of greenlighting stuff.

    4. Re:And LibreOffice is already merging improvements by jensend · · Score: 3, Insightful

      There might have been a lot of people who were willing to dual-license most of their contributions, but you turned a *lot* of them off with your toxic attitude and the juvenile bullcrap you have been spewing for the last several years on mailing lists and fora. Now, years after flaming potential collaborators enough that they were unwilling to put up with you, you point to a token few dual-licensers as a resounding success.

    5. Re:And LibreOffice is already merging improvements by jensend · · Score: 2

      What rebuttal of what claim? Do you have me confused with someone else? I made no claims prior to what you're characterizing as an "ad hominem attack."

      Ad hominem is only fallacious when it's an irrelevancy. In a discussion of community and contributions, the fact that you have turned many people away from the OpenOffice community with your behavior is acutely relevant.

    6. Re:And LibreOffice is already merging improvements by Palestrina · · Score: 2, Interesting

      You were either attempting to argue against my claim that there were contributions from LibreOffice coming back into Apache OpenOffice, in an ad hominen attack. Or you were merely interjecting irrelevancies. I'm willing to accept that you were merely being irrelevant. In any case you never bothered to substantiate *any* of your claims so I waste no time rebutting them.

  7. Sidebar! by whoever57 · · Score: 5, Insightful

    Finally, somthing that makes sense on 16x9 monitors, instead of the idiotic idea of taking up vertical space in a "ribbon"

    --
    The real "Libtards" are the Libertarians!
  8. No Worries, LibreOffice got you covered by Anonymous Coward · · Score: 3, Informative

    Don't worry, LibreOffice already has all the improvements imported from Apache, see https://www.libreoffice.org/download/4-1-new-features-and-fixes/

  9. Re:PC is not a tablet by SJHillman · · Score: 5, Insightful

    Given that it's damn near impossible to find a 4:3 monitor larger than 17" and very hard to find even 16:10, it makes more sense to put in sidebars to use the abundant horizontal space rather than the vertical. Of course, once you get to around 24" monitors, it starts to become much more commonplace to have two apps side-by-side, in which case the argument goes back to having toolbars on the top and bottom.

    Or we could, you know, have both as options.

  10. Never thought I'd see the day by sl4shd0rk · · Score: 2

    *Two* open source offerings competing against each other instead of against Microsoft.

    --
    Join the Slashcott! Feb 10 thru Feb 17!
    1. Re:Never thought I'd see the day by Tough+Love · · Score: 2

      Then you haven't been paying attention.

      --
      When all you have is a hammer, every problem starts to look like a thumb.
  11. Re:They seem to be doing a fine job. by Anonymous Coward · · Score: 5, Interesting

    This is garbage. 5% of contributions to LO 4.1 came from apache.

    Claiming everything came from apache is an IBM marketing lie and they've been called out on it.

  12. Sidebar the differentiator - really? by JImbob0i0 · · Score: 4, Interesting

    Well since they laud the new sidebar so much for better use of widescreen monitors they should love the fact that LibreOffice will have it within a few days...

    4.1 is due in a matter of days which has an improved sidebar that's resizeable and not just a static part of the screen.

    I really question what the point of AOO is at this juncture given that LO is clearly the more active project and has two years of code clean up and development over AOO due to the way Oracle let it stagnate for so long.

    If you want to try 4.1 now it is on the pre-releases page and it's the final RC there ... ie the same that will be released as final GA in a few days.

    1. Re:Sidebar the differentiator - really? by Palestrina · · Score: 2, Informative

      Too bad users use the product and don't gain direct productivity merely from looking at Ohloh stats.

      But if they did, the numbers you point at show an interesting story. It shows that the average AOO contributor makes twice the number of commits as the average LO contributor. And the average AOO commit is far more significant, touching twice the number of files as the average LO commit. Net it out and the average AOO contributor is 4x as productive compared to the average LO contributor!

    2. Re:Sidebar the differentiator - really? by JImbob0i0 · · Score: 3, Interesting

      Too bad users use the product and don't gain direct productivity merely from looking at Ohloh stats.

      But the stats do paint the picture of the direct benefit to the users...

      See all those deleted lines? That's code clean up that is... That means less bugs and easier to maintain and also easier for new people to help with when they get an itch they need to scratch.

      It shows that the average AOO contributor makes twice the number of commits as the average LO contributor. And the average AOO commit is far more significant, touching twice the number of files as the average LO commit. Net it out and the average AOO contributor is 4x as productive compared to the average LO contributor!

      Way to twist the statistics...

      In a way what you say is absolutely true but then that misses the mark but quite an impressive amount. It's almost to the point I feel a need to call you out on this as being literally true so no one can call you a liar but that truth being represented in such a way as to mask the real situation.

      The recent libreoffice blog post covers the the growth of committers and includes a brief discussion of "the long tail" with a large number of people in the community submitting small fixes here and there because they can and to scratch a small itch... this is not happening on the AOO code base.

      To me that shows a healthier development community of in the LO camp.

      Put it this way if a project has 100 people each committing to 2 files over a code base and another project which had 2 people committing to 100 files over another fork which would you say was "more productive" and would you equate that with project healthiness?

    3. Re:Sidebar the differentiator - really? by JImbob0i0 · · Score: 3, Informative

      The point is that without the Apache guys there wouldn't be a sidebar in either project. LibreOffice has done a lot of stuff but none if it is as visible as the Apache guys have done.

      This is nonsense... The sidebar stuff wasn't written by anyone in Apache - it was IBM code from the symphony project/fork donated to Apache that was then merged into AOO and merged (with small improvements like resizing) into LO as well...

      As for the not visible bit have a look through the new features and fixes in 4.0 and 4.1.

      There's a lot of nice new content with visible useful features such as chart import and export as both ODC and images in calc, presentation mode in Impress, visio import in Draw (that was LO 3.5), huge reduction of java dependencies, refactor how calc views cells internally for much faster performance on large spreadsheets, MS Publisher import, and the list goes on ....

      As for letting the code speak for itself ... yes please do and it's obvious which project is currently healthier and better overall.

    4. Re:Sidebar the differentiator - really? by Anonymous Coward · · Score: 2, Informative

      > In a way what you say is absolutely true but then that misses the mark but quite an impressive amount. It's almost to the point I feel a need to call you out on this as being literally true so no one can call you a liar but that truth being represented in such a way as to mask the real situation.

      Yeah, that was some "interesting" statistics. But it is really easy to refute. In the last 12 months there were 52 developers on the Apache side (note they include people "hacking on the website" and 351 developers on the TDF/Libreoffice side (who are "pure" code hackers, website, etc is done by other people). Now lets just pretend those 300 "extra" LibreOffice hackers aren't there. Just look at the top 50 hackers on both sides. Also on Ohloh you can find that the 50th most active Apache hacker did 2 commits in the last 12 months, the 50th most active LibreOffice hacker did 53 commits the last 12 months. To get to the contributor in LibreOffice that only did 2 commits in the last 12 months you need to go down all the way to contributor number 150 (!).

      Or the other way around, the top contributor to Apache (rcwier an IBM manager who mainly does HTML edits) contributes 755 commits in the last 12 months. The top 8 LibreOffice hackers contribute more than that number of commits (and all of them actual code, not just website promotion edits).

    5. Re:Sidebar the differentiator - really? by Palestrina · · Score: 3, Insightful

      It is not quite true to say this was just a merge from Symphony. Actually, your statement is entirely false. The core Sidebar was reimplemented in AOO 4.0, by developers at Apache. One of the core goals was to make it a framework that could be used by Extension authors as well.

      You can read more details on this in this blog post:

      https://blogs.apache.org/OOo/entry/the_sidebar_new_and_improved

      And as I've said before, it is regrettable that LibreOffice supporters find it so difficult to graciously accept good code from a good project. No one, absolutely no one, is complaining about you using it. It is under the Apache License, free for LibreOffice or anyone else to use it, now and forever. Although the license says nothing about polite manners, and I never expect to hear even the smallest statement of thanks, I think the larger open source community does find it disturbing that LibreOffice supporters are so eager to take code from AOO while continually insulting it at the same time. Remember, using code from other open source projects does not make you smaller. We all "stand on the shoulders of giants", so try not to piss on them, or upstream in general.

    6. Re:Sidebar the differentiator - really? by Dawn+Keyhotie · · Score: 4, Insightful

      "No one, absolutely no one, is complaining about you using [AOO source]."

      And yet here you are, trolling on Slashdot, badmouthing LO and its supporters at every turn.

      LO gives credit where credit is due, on their site and in their documentation, and I have yet to see any LO contributor or TDF member badmouth AOO in any public forum.

      And AOO is not "upstream" of LO. LO is an independent project and makes its own decisions regarding the incorporation of contributions from other projects. It is a true fork of the original source code, and does not simply repackage whatever AOO ships.

      You did good work with the OOXML standardization coverage a few years ago, but these LO/AOO diatribes are doing a disservice to your reputation.

      --
      "The only good windmill is a tilted windmill."
    7. Re:Sidebar the differentiator - really? by Palestrina · · Score: 2, Interesting

      I hope you know that you did not address my argument at all but merely attacked me personally.

      There was a false assertion that the Sidebar was not done at Apache. I rebutted that. I then remarked that LibreOffice *supporters* seem to have difficulty graciously accepting the fact that the most notable feature of LO 4.1 is coming from Apache. You responded by saying that you have never seem a TDF member saying anything bad about AOO. That is irrelevant, since that was not my claim. And it is also untrue since I could point to ample examples of this.

      From my perspective LO is downstream. A look at their logs shows that their use of AOO code is frequent and routine. They are not occasionally cherry picking, but deliberately mining every relevant patch:

      http://cgit.freedesktop.org/libreoffice/core/log/?h=aoo/trunk&showmsg=1

      In any case, I imagine this large scale use of AOO code is a source of some cognitive dissonance for them, after spending so much time trying to convince themselves that having a fork was better than working together with Apache, arguing that nothing good would ever come from Apache. Now they are faced once again with the inconvenient facts, that the AOO code is good, it is worth taking in large quantities. In fact their users are demanding this. TDF members were beaten up quite a bit at a recent conference from users demanding to know when they would improve their UI like Apache was. Somehow they need to reconcile these facts and their actions with their ongoing stance of non-cooperation with Apache.

  13. Reveal Codes? by TCPhotography · · Score: 2

    Does it have a WordPerfect-like Reveal Codes feature?

    No?

    No dice.

  14. Here we go again by sproketboy · · Score: 3, Funny

    Here we go again with all the ranting about the mexican wrestler version. *sigh*

  15. Re:PC is not a tablet by just_a_monkey · · Score: 4, Funny

    Or we could, you know, have both as options.

    That's crazy talk.

    --
    How inappropriate to call this planet Earth, when clearly it is Ocean.
  16. Re:PC is not a tablet by just_a_monkey · · Score: 2

    Strange how no-one "rejected change" in any other office version. Except for the one with Clippy.

    --
    How inappropriate to call this planet Earth, when clearly it is Ocean.
  17. Re:I give up on WISYWIG by kasperd · · Score: 3, Insightful

    I now use LaTeX because I just get the job done and done well.

    WISYWIG is evil, we need to go back to WRITING our documents rather than dicking about with font sizes and colours.

    As an added benefit you can store your documents in a source control system such that you can actually keep track of changes. (The change tracking I have seen build into some office suites was fundamentally flawed. They could only compare with one previous version and not show in which order changes were made. And they were relying on all the software used by the various parties to accurately record what was changed. Not really useful as anything other than a toy.)

    --

    Do you care about the security of your wireless mouse?
  18. Re:They seem to be doing a fine job. by Palestrina · · Score: 3, Interesting

    I'm sure you can make the huge contribution of the AOO Sidebar look numerically 5% if you do two things:

    1) Count the entire Sidebar UI as a single commit, which Ohloh does because the work was done on a branch, not the trunk. (Ohloh counts only the AOO trunk)

    2) Bloat your own commit counts with insignificant "behind the scenes cleanup" like translating German comments, or other stuff that no user will ever benefit from.

    But if you look at features of actual significance, what the users actually want and will benefit from, the code from Apache is actually quite significant in LibreOffice.

    I wish LibreOffice supporters would stop acting like it makes them small to acknowledge some gratitude to other open source projects which they are dependent on.

  19. NSA's backdoor by beefoot · · Score: 2

    I don't know about you, I feel like exposing my erotic story I write to NSA. If openoffice does not have a back door to NSA, it will not cut it for me. Just saying.

  20. Re:Merge Already! Libre/Open by Anonymous Coward · · Score: 4, Interesting

    Nothing like one-way leeching to keep a project going. Seems silly to split because of lack of activity from Oracle and then devolve into leeching changes from Apache.

  21. Re:They seem to be doing a fine job. by Palestrina · · Score: 4, Insightful

    Comment? Yes. Of the various approaches to argument, the strongest one is to take your opponent's most valid point, the key of their argument, and then to logically rebut it. On the other hand, one of the weakest arguments is the ad hominem attack, declining to engage logic entirely and instead trying to win by bravado and superficial slight of hand. I dismantled your argument, by showing the flaws in how you calculated and interpreted your "5%" claim. You responded (no not responded, but dodged entirely) with an ad hominem attack. I assume if you had a stronger argument to make you would have done so.

  22. Re:LAWL @ "Letting the code speak for them" by Palestrina · · Score: 2

    I don't think it is juvenile at all to point out that comparisons of committer counts is meaningless where the contents of the commits, in terms of how many files are changed, varies by a factor of 4 between the projects. The difference in VCS used as well as what kinds of contributions are measured by Ohloh (and are not measured) makes any naive comparison hugely problematic. In fact I'd say it is intellectual dishonest to perpetuate these kinds of apples to oranges comparisons. On the other hand, if your only story is Ohloh code statistics, what else are you going to do?

    Rather than looking at the code, I've focused more on looking at the users, doing apples-to-apples comparisons, looking at name recognition, usage stats, user satisfaction, etc., comparing OpenOffice and LibreOffice. And the real world numbers show LibreOffice is in a bad position and declining:

    http://www.robweir.com/blog/2013/06/the-power-of-brand-and-the-power-of-product-part-2.html

    So please, tell us more about how many lines of code were removed by your long tail. We'll all entranced and want to hear more about how hard you think you are working. But also occasionally take a peak at the real world and see how you are really doing. There is a big difference between riding a stationary bicycle in a gym versus traveling cross country. Personally, I think LO is mainly churning code and spinning its wheels, though the sweat you feel is real.

  23. Re:Merge Already! Libre/Open by Tough+Love · · Score: 3, Interesting

    If Libreoffice does end up dominating (Openoffice still has the most old and new users because of inertia and name recognition) then it will be convincing evidence of the evolutionary superiority of copyleft.

    At this point I'm betting on Libreoffice + LGPL. Hope I don't get any "libertarian license" jihadis steamed about that, but this just seems like reality.

    --
    When all you have is a hammer, every problem starts to look like a thumb.
  24. Re:LAWL @ "Letting the code speak for them" by jensend · · Score: 3, Interesting

    I'm not a Libreoffice developer, just a reader of these fora and a former OpenOffice user who is sick and tired of reading your bull. (I originally left OO because your license purge removed features I needed; so much for your silly attempt in another post to try to take the "pragmatic high ground" by characterizing LO's position as "that license bullshit.")

    I'm not interested in hearing your eternal rationalizations about why your statistics are so much better than LO's. I've been hearing this crap for years now. You start frothing at the mouth any time somebody says something positive about LO, you don't release anything notable for 2 1/2 years, and you call this "letting the code speak for you."

    Meanwhile LO may

  25. Re:LAWL @ "Letting the code speak for them" by jensend · · Score: 2

    Aargh, mistakenly submitted when I brushed off something that'd fallen on my keyboard.

    Anyway, meanwhile LO may commit the oh-so-very-grievous sin of putting out some PR once in a while trying to promote their project, but they don't waste their breath continually trying to tear AOO down. Instead they've busily been putting out a stream of releases with features I needed. That's who's letting the code talk for them.

  26. Re:Merge Already! Libre/Open by evilviper · · Score: 4, Insightful

    They are merging! LibreOffice imports all useful bits.

    Is that the same way Linux and FreeBSD are "merging"?

    And yet Linux doesn't yet have a modern file system...

    ZFS works great on FreeBSD. HAMMER from DragonFly BSD is damn good as well. BTRFS still sucks, YEARS after it SHOULD HAVE been stable.

    Having a license that supposedly allows you to suck the marrow out of the upstream project doesn't really solve your problems for you, and you can certainly still fall behind.

    If the LibreOffice guys were smart, they'd be contributing as many of their changes as possible to the upstream project, so they won't have to do extra maintenance, and more people would benefit from them. Of course, if those LO guys were smart, they would have picked a slightly less horrific and painful NAME for their project...

    --
    Slashdot gets worse every day... Pipedot: News for nerds, without the corporate slant
  27. Re:Merge Already! Libre/Open by JImbob0i0 · · Score: 3, Insightful

    If the LibreOffice guys were smart, they'd be contributing as many of their changes as possible to the upstream project,

    Can we please get past calling AOO the upstream project of LO? This is like calling gorillas the upstream project of humans...

    Yes they share a common ancestry but that is it at this point... sure some stuff can be transplanted from one to the other but there is no upstream/downstream relationship that one would usually understand that term as in the FOSS world (eg Fedora -> RHEL).