Probably an unpopular thing to say here, but in my experience pushing non-tech people to use libreoffice as part of a Linux transition is a fast track to getting them to hate Linux.
Using Google Docs has been much more welcoming in my experience. Something about libreoffice doesn’t resonate with a lot of non-tech people.
I'll grant that it's personal preference and OP should do what his customers prefer, but what you said is a good thing. UIs have sucked for some time now, so something which deliberately uses an older style is generally far superior.
Categorized ribbon is an improvement for most people. Especially new generations who simply can't enjoy the effect of shared conventions with other software.
> LibreOffice is a UI time capsule..more archaeology than productivity.
I agree. Seeing the comments here claiming the outdated UI is a good thing, actually, brings up one of the big problems with a lot of open source and/or Linux soecific software: The resistance to UI change is huge among die-hard users so the projects tend to get stuck in whatever UI language they had a decade ago when they started
When I introduce people to open source versions of different software I find myself starting with “The UI has a steep learning curve, but…”.
It would be so much easier if we could give people apps that were targeted at familiar UI patterns of today, even if it angers a vocal minority who want every UI to look like it came out of the 90s or early 2000s when they first discovered their love of computers.
Oh, worse: stuck in whatever weird, half-baked UI decisions that were made because someone had a great idea that they did not test at all, or because they hated the industry standard approach that everyone else uses. It's no secret that Blender adoption exploded when they added normal menus, and then made right-click select an optional function, and then finally added an auto Maya-like interface option.
But that's one instance where we lucked out. Not just because they fixed it, but also because the thing that needed to be fixed was in users' face and obvious.
My understanding is that the issue is the way OO/LO and the OS work together to handle file writes, which will not be changed because Linux distros do it right and Windows does it wrong and too bad that I was trying to use OO on a Windows PC. But I can't get a straight answer, and even if I were to, it wouldn't fix the bug - because the bug would be that I was using Windows. And now that I know that this is something that happens, I don't have any real guarantee that tomorrow the problem won't be the particular distro that I use, or whatever weird personal ax-to-grind led to the design decision that would now be giving me a headache. And that probably goes doubly for your average Windows user who doesn't really know what they're getting into.
Obviously, Google's support situation isn't any better. They've also had their share of catastrophic data loss fun-times. I genuinely don't know what the answer is.