Earlier quoted context omitted.
LibreOffice is a noble yet doomed project that tries to fix the unfixable: the incredibly slow, highly complicated and unaesthetic StarOffice originally developed by Sun, that later reincarnated in OpenOffice. Fixing that suite is so monumentally effort intensive that you would be better off rewriting it from scratch or porting features to a simpler suite like Abiword/Gnumeric, etc. FreeOffice is the free version of…
Is LibreOffice really that slow? Sure, it takes a while to start up, but after that my experience has been that it's as performant as Microsoft Office or Google Docs (ie. pretty much instant for everything I've done with it). Just start it once and keep it running, and you won't really have to worry about performance. As for aesthetics, it looks fine to me... just like any other generic office app... besides which, a…
Red Hat dropping support for LibreOffice
121–130 of 316 posts
Re: Red Hat dropping support for LibreOffice
#122WYSWYG office suites were a mistake. Combining the editing and the display compromises both. They seem destined to become giant unmaintainable monoliths. They solve problems that are fundamentally really hard but also incredibly boring, like making layout decisions on the fly. And finally they are just boring in a way that means nobody is really that interested in contributing. Markdown, LaTeX, or HTML are much bette…
Re: Red Hat dropping support for LibreOffice
#123Earlier quoted context omitted.
AppImage is also troublesome. I just spent a good while debugging ours. The TL;DR is that AppImage amounts to a self-extracting archive, and you need an application where all the binaries and libraries have a relative rpath. So rather than loading /usr/lib/libz.so, it uses $BINARY/../lib/libz.so. That part's not too bad, but what can cause a lot of trouble is that there's a fair amount of stuff that uses dlopen at ru…
And AppImage distribution has the same fundamental security problem as static binaries, making it difficult or impossible to replace downstream dependencies. When a dynamic library needs a security update (e.g. heartbleed in libssl), the shared library can be replaced system-wide. When a static executable or AppImage needs a newer version of a library, you need to update the program entirely, and there is no way to d…
But on a system where everything is updated at the same time through a package manager, I don't see that there's a material difference, unless you as the upstream app developer decide not to build against the latest security updates of your dependencies; but if that's the case, that's a completely separate issue from dynamic vs. static linkage.
Re: Red Hat dropping support for LibreOffice
#124Earlier quoted context omitted.
I always find this take so weird. Do you audit every single line of code from OSS you use?
I don't read every line of code but yeah. I think I spend more time reading code for curiosity's sake than actually using many programs. I absolutely read build system scripts, I won't run make until I know what's gonna happen. I also enjoy stracing random programs in order to figure out the exact set of system calls they're making, in which order and with which parameters.
Re: Red Hat dropping support for LibreOffice
#125Re: Red Hat dropping support for LibreOffice
#126Earlier quoted context omitted.
What's more important for most users, document editing or image/video editing?
That's a false comparison. You can still edit documents using LibreOffice installed via flatpak, or, like probably most users, use Google Docs, Office 365, or OnlyOffice. Meanwhile without proper HDR support and better color management, Linux desktop is basically a non-starter for any professional creative use-case, including design, animation, illustration, image and video editing. Ideally both would be done but the…
Re: Red Hat dropping support for LibreOffice
#127Microsoft also apparently going large scale with CentOS-based Azure Linux.
The question is: What is the best solution going forward for desktop productivity software on Linux?
Re: Red Hat dropping support for LibreOffice
#128Re: Red Hat dropping support for LibreOffice
#129Earlier quoted context omitted.
> If it does not make sense business-wise, it's their call. I'm pretty sure they know their userbase and did the math. This assumes companies don't make mistakes. They do. A lot. And if users aren't allowed to voice concern then they will make many more mistakes.
> And if users aren't allowed to voice concern then they will make many more mistakes. Generally, RHEL does exactly what RHEL customers want. They are extremely loyal to their user base. The issues come when these changes set a trend and ripple to the rest of the community, and affect people who would never become a RH customer in the first place (e.g. anti-systemd fanatics)
But this is still an odd statement. Previous customers who very much relied on LibreOffice might move to some other platform or at least some other support service. Thus they would no longer be Redhat customers and Redhat would still be loyal to their customers.
I suspect the number of RHEL Workstation customers to be a relatively small part of Redhat's customer base. And those that depend on LO support to be even smaller. I don't expect this to affect RH's bottom line in any negative way.