[HN Gopher] LibreOffice 24.2 Will Succeed LibreOffice 7.6
       ___________________________________________________________________
        
       LibreOffice 24.2 Will Succeed LibreOffice 7.6
        
       Author : profwalkstr
       Score  : 47 points
       Date   : 2023-08-22 21:49 UTC (1 hours ago)
        
 (HTM) web link (www.phoronix.com)
 (TXT) w3m dump (www.phoronix.com)
        
       | jokoon wrote:
       | I learned that I can just add a picture in a PDF with libreoffice
       | draw, which is a thing that cannot be done with pdf.js yet.
        
       | actionfromafar wrote:
       | Will someone turn off the lights at OpenOffice? It's so sad.
        
         | graypegg wrote:
         | Just as a note since it's not 100% clear which project you're
         | talking about, LibreOffice and OpenOffice are now two different
         | projects. One is just a fork of the other.
         | 
         | LibreOffice (the topic of this article and version change)
         | isn't very sad imo!
        
           | taneq wrote:
           | I interpreted this as "LibreOffice supplanted OpenOffice so
           | completely and so long ago that OpenOffice should just give
           | up." (Not up to date with what or how the OpenOffice project
           | is doing these days so I have no opinion on them personally,
           | I always thought LibreOffice was essentially just a re-brand
           | though?)
        
             | actionfromafar wrote:
             | OpenOffice is limping along, about a gazillion commits and
             | bugfixes behing LibreOffice. To match your Internet
             | Explorer 6 experience, try OpenOffice today!
        
             | ethbr1 wrote:
             | Afaik, LibreOffice was a fork of OpenOffice because
             | OpenOffice refused to implement quality of life features in
             | a timely manner.
             | 
             | https://en.m.wikipedia.org/wiki/OpenOffice.org#LibreOffice
             | 
             | Apparently there was also some footdragging by Sun (because
             | Sun) and later Oracle (because evil) about creating a
             | neutral caretaker foundation to guide development.
             | 
             | Circa 2010/11, the development community decided to do it
             | themselves.
        
       | isaacremuant wrote:
       | Clickbait title but makes sense. Yearly versioning.
        
         | calvinmorrison wrote:
         | Which tells you less than a actual semver. Where did it all go
         | wrong?
        
           | jacobsenscott wrote:
           | lol. "Breaking change: all English text is rendered right to
           | left now. In can be changed to bottom to top in the compile
           | options. Left to right has been removed."
        
           | throwbadubadu wrote:
           | Just read the intro of https://semver.org/ once more, maybe
           | you notice something?
        
           | quonn wrote:
           | It's not less but different. For example you immediately know
           | how old the version is.
        
           | theossuary wrote:
           | Calendar versioning makes way more sense for end user
           | applications, especially those with GUIs. There isn't much
           | concept of a non-backwards breaking change in something like
           | libreoffice, so semver ends up trying to expose information
           | that isn't there.
        
           | msla wrote:
           | Semantic versions only make sense if you anticipate
           | discontinuous breaking changes in the future, with periods of
           | stability between. If no new version will be a breaking
           | change, or if every new version will be breaking, it loses
           | meaning and you might as well go date-based. (Or, if you're
           | Linus Torvalds, completely arbitrary.)
        
             | JohnFen wrote:
             | > If no new version will be a breaking change, or if every
             | new version will be breaking
             | 
             | But the vast majority of the time, applications fall into
             | neither of those categories.
        
           | skissane wrote:
           | I don't think semver is very useful for applications as
           | opposed to libraries.
           | 
           | Remove some obscure feature which almost nobody ever used?
           | Backward incompatible change, must increment major version.
           | 
           | Add some major new feature which is a massive quantity of
           | code, visible and likely important to all users-but 100%
           | backward compatible? Increment minor version instead.
           | 
           | Make sense to (some) developers, but to an end-user semver is
           | rather nonsensical. Everyone can understand calendar-based
           | versioning.
        
             | JohnFen wrote:
             | But semver actually tells you useful information. calendar-
             | based versioning tells you nearly nothing.
             | 
             | To end users who only care that they have the latest
             | version, both schemes serve the purpose equally well, so
             | why not go with semver?
             | 
             | But I'll take even calendar-based over code names. Code
             | names tell you literally nothing.
        
           | ahofmann wrote:
           | Semver is perfect for developers and libraries and helps a
           | lot.
           | 
           | In software for end users semver tells nothing most of the
           | time.
        
             | deaddodo wrote:
             | SemVer is more useful in Apps if you use feeling vs strict
             | rules. A massive UI overhaul (but without breaking
             | features) is almost definitely a major version bump but
             | SemVer says it's a significant minor jump (5.0->5.5), at
             | best.
             | 
             | The problem is that SemVer was released _for_ libraries,
             | where it 's rationale and rules make sense. But the
             | abstract _spirit_ of major.minor.patch makes more sense at
             | an application level.
        
         | michaellarabel wrote:
         | How is the title 'clickbait'? Calling It "LibreOffice Changing
         | To Year.Month Based Versioning Scheme" or similar just makes it
         | longer and less immediately clear... Really I honestly fail to
         | see how it could be considered 'clickbait' for phrasing it as
         | simply as possible.
        
           | xcdzvyn wrote:
           | The title is definitely supposed to play on the shock factor
           | of 24 clearly not being immediately greater than 8, and
           | possibly the mixed reactions to some other software moving
           | away from SemVer (Firefox switching to Chrome's scheme comes
           | to mind)
           | 
           | It wasn't immediately apparent to me that the new versioning
           | scheme would be year.month/whatever, which is the real news,
           | but it's less interesting.
        
             | TaylorAlexander wrote:
             | The title is a simple factual statement. I see no reason to
             | presume the information is presented for "shock factor".
        
       | jsight wrote:
       | Is LibreOffice still commonly used? It seems like much of the
       | world has shifted to cloud offerings.
        
         | jehb wrote:
         | I use it all the time, not because I'm as good as I'd like to
         | be about keeping things out of the cloud that don't need to be
         | there, but because I often have ad hoc spreadsheets that are
         | bigger than Google Sheets can handle.
        
         | Scarbutt wrote:
         | Exporting to .xls files it's pretty bad, so it's a no for
         | sharing. Unfortunately, Google sheets does a better job here.
        
         | badsectoracula wrote:
         | I use it all the time when i need a spreadsheet, rich text
         | editor or... powerpoint viewer :-P.
         | 
         | Now i don't really need these _that_ often but it is still one
         | of the programs i have installed on my PC since the OpenOffice
         | days.
         | 
         | Also FWIW i avoid anything web-based as much as i can. I prefer
         | software that runs on my own PC, as a desktop app whenever
         | possible.
        
           | LoveMortuus wrote:
           | Interesting, I used to use word processor that aren't cloud
           | based, but many years ago I've lost to many of my writings
           | due to crashes or power loses, do that when I finally
           | discovered cloud based word processors it was like magic to
           | me, because it didn't crash and if I lost power I didn't lose
           | any of my work!
        
         | blackhaz wrote:
         | Daily. I hate clouds with a passion.
        
         | gillesjacobs wrote:
         | The killer feature for me is full regex search and replace
         | support, not available elsewhere.
        
       | cheaprentalyeti wrote:
       | They could do like Slackware and go to version 13.37...
        
         | nvy wrote:
         | I'm waiting for v31.337 myself
        
       ___________________________________________________________________
       (page generated 2023-08-22 23:00 UTC)