Technology

Sometimes it is better to start fresh.

Especially when you want to be the owner of something.

Libre has 35 years of good, bad, and the ugly. It's has 35 years of tech debt, and design choices made. That's not easy to just "fix"

It's a completely different beast to sift through legacy code than it is to just start fresh requiring a completely separate set of skills.

Not getting rid of the old is one of the many reason Windows is such a shit show. Every program today in 2026 asks itself "Am I Barbie Riding Club(1996)? Before it runs because it needs a special compatibility mode". Why inherit among the million other issues if you don't want to?

Technical debt is a thing. Everyone says Xorg is too old to be maintained so we have to switch to Wayland for example. I don't know the state of Libre Office but it's possible it simply can't be easily migrated to newer, better tools.

Old isn't necessarily bad, unless years of decision-making have left it in a massively complex state (see also: Xorg)

The real reason here is that LibreOffice is written in C++, which is falling rapidly out of fashion for modern apps, leading to a smaller supply of developers.

Contrast this with Onlyoffice. Yes, the document engine is still written in C++, however the build tools use more modern items like python and onlyoffice supports having Javascript frontends and scripting, making it easier to source web devs to work on these parts.

Maybe liberation office, or just LibreOffice for short.

The issue is that a lot of processes need to be understood by people who have no IT background. Your basic office drones need to be able to use it, enter data, and make changes. Every applicant in an office job will be relatively proficient in Excel.
If you move your process to another solution, the majority of your employees will have to be re-trained.

As a data consultant, I would say those companies already do question the process, and have done for decades.

Yes there are countless situations where a dedicated system or database could and should replace Excel, but there are just as many scenarios where Excel is ideal, and swapping out a spreadsheet for what would be potentially tens of separate applications across the business, or one absurdly expensive behemoth, to perform tasks that could be done rapidly and clearly in Excel is neither practical nor economically viable for most companies. A spreadsheet is perfect for plenty of situations.

My job is literally to help these companies move to appropriate database solutions, often transitioning away from Excel. But there’s no getting around that a spreadsheet solves (often simple) problems that are impractical with other tools. You can move a company to a supplier’s sector-specific solution and solve huge numbers of issues, but unless that solution exactly meets every aspect of the business requirements, there’s always going to be a fallback and it’s often Excel, for better or worse.