LibreOffice Calls Out Microsoft For Using 'Complex' File Formats To Lock in Office Users (neowin.net)
- Reference: 0178411764
- News link: https://it.slashdot.org/story/25/07/18/1811216/libreoffice-calls-out-microsoft-for-using-complex-file-formats-to-lock-in-office-users
- Source link: https://www.neowin.net/news/libreoffice-calls-out-microsoft-for-using-complex-file-formats-to-lock-in-office-users/
LibreOffice compared the situation to a railway system where tracks are public but one company's control system is so convoluted that competitors cannot build compatible trains.
[1] https://www.neowin.net/news/libreoffice-calls-out-microsoft-for-using-complex-file-formats-to-lock-in-office-users/
Don't spread the Word (Score:1)
The only thing locking anyone in is ignorance. So spread the word! Wait, don't...
Format (Score:4, Insightful)
So you have a file format going back almost 20 years, that supports embedding almost any kind of content anywhere, that has had new features bolted on almost constantly, and also is backwards compatible so that anything not using a new feature is readable by older applications, and is also forward-compatible so newer versions of the application can render these documents accurately. And people complain that said file format is too complex?
For a comparison, go read up on how complex the TIFF standard is, and that is, basically, a bunch of numbers corresponding to color values in a bitmap. The ancient base-standard document is 120 pages long.
Re: (Score:2)
Yeah. pretty sure it is not intentional. It's just years of kruft stacking on top of each other. They could probably clean up the specification, but it would break stuff left and right. One thing Microsoft actually does well is backwards compatibility. Sometimes you just gotta clean house though.
Re: (Score:1)
> One thing Microsoft actually does well is backwards compatibility.
Odd, I haven't seen that. I have tons of old powerpoint presentations where half the images are replaced by a huge red "X" because the new powerpoint won't deal with them.
When I need to open old files, I use Libre Office.
--
(apologies for posting AC-- had a few mod points to burn).
Re: (Score:2)
Yes that explains the complexity, but not the ongoing bad naming of the options.
Re: (Score:2)
That's the weakest complaint. If the bad option names are documented, so what? You have to read the spec to know what to do anyway. If they aren't documented, complain about that.
Re: (Score:2)
I once had to re-implement an application based on specification document. When doing that, several times I encountered a situation where I noticed that the documentation was not specific enough. I then realized that it would be extremely helpful if a specification would come with a sample code that implements it.
Re: (Score:1)
That's one of the two big complaints about OOXML: that Microsoft took their old binary formats (which, as you alluded in your post, were a essentially memory dump of the application's memory with new features overlaid on top of old ones), gave the fields meaningless names, and dumped them into XML. This was beneficial to Microsoft because they didn't have to write any complex conversion code (from the old binary formats to OOXML and vice-versa), but it's not the ISO-class format they promised the world (yet
Re: (Score:3)
Can't find any concrete references (too lazy). But I remember many of us (here on Slashdot and other dens of iniquity) laughing at the insanity of the OOXML format when it first emerged. Especially given the pre-existence of ODF.
The [1]Wikipedia page [wikipedia.org] does tell us the number of pages the standard runs to - it's greater than 120.
It also suggests there have only been two major releases of the format and the problems seem to have been baked in from day one.
[1] https://en.wikipedia.org/wiki/Office_Open_XML
Obilgtory old joke still applies today: (Score:2)
Q: How many Microsoft engineers does it take to change a light bulb?
A: Zero. Microsoft simply declares Darkness the new Standard.
been there done that, educate yourself (Score:2)
I've spent time on the difficult end of black-boxing a BINARY file format. You jokers with your XML and LABELS have it faaaaaar too easy. Here, I'll tell you my secret:
Gather as many saved files as you can, from as diverse of a group as possible. (there is NO upper limit, literally grab as many as you can) Write a short little test script to import and then export every single one. Then compare the export with the original. Refer the mismatches to the dev. I had over 1,000 test files in my suite, and
Microsoft committing anti-competitive behavior? (Score:1)
My stars and garters! Fetch me my fainting goats!
Every now and then nerds will realize that their computer is kind of suck because we don't enforce antitrust law but we always go back to sleep.
LaTeX (Score:2)
\documentclass{slashdot}
\begin{document}
\LaTex is the one true format. All others are trash.
\end{document}
Re: (Score:2)
Indeed. And ODF is not that much worse.
Re: (Score:2)
Yeah, after you get used to it, LaTex works quite well. I do my manuals in it and have for years. Originally I used Frame back when Sun was a thing. Both Frame and LaTex have one huge advantage over MS, or at least used to. Size. You can do 3K page docs no problem in LaTex. A friend who was a tech writer would moan bitterly about MS products crashing if the client demanded she use MS.
It's open but unnecessarily complex (Score:2)
... is the name of the Free Software anthem. Maybe not fair to lump all projects together but we're cutting really close to stone thrown from a glass house.
Re: (Score:2)
^This^
That's always been my issue with the *Nix stuff... sure, it might run fine and be more stable (and if a user has the programming knowledge, completely editable to whatever they can dream up), but for the vast majority, it's too complex to get it running without having to read a document the size of the Bible, let alone open a file made in Office 2016 or whatever (whether it's a PowerPoint or Word or spreadsheet document).
While FOSS is a great idea, the problem is compatibility.
The general purpose of a
No problem (Score:2)
> Microsoft's OOXML format includes deeply nested structures with non-intuitive naming conventions and numerous optional elements that make implementation difficult for developers outside Microsoft.
Just have Copilot refactor and document the format.
Good old crooked Microsoft (Score:3)
Because anti-competitive behavior is just that: Not competing on merit but instead scamming users and competitors. I hope there will be another massive fine from the EU incoming. Because obviously, there is absolutely no need to do it this way on the tech side.
Re: (Score:2)
It sounds like you're venting about a Microsoft-branded bug up your ass until the last sentence, which makes it seem like it's all been sarcasm. Was that your intent or am I reading you wrong?
Intentional? (Score:2)
I doubt it.
In my experience, the most complicated code comes from the hands of lower-skilled developers. It takes skill, knowledge, and intelligence, to produce code or file formats that are elegant and usable.
To the extent that they're right about the format, I highly doubt that it was *deliberately* complex.
Current formats much less complex than the old (Score:2)
Remember .xls, .doc, and .ppt files? They were both complicated and binary. The BIFF format, used in Excel, had a binary format built on record identifiers and length indicators, followed by variable-length data where each record type had an entirely different format from the other record types. Further, if you embedded a chart or image in an Excel file, the bytes of that blob were broken up into chunks and interspersed in the file at almost random intervals, with individual blobs cut right in the middle of
Bill Gates on StarOffice patent violations (Score:2)
From: Bill Gates
Sent: Monday, December 07 1998 8:28 PM
To: Jon DeVann; Steven Sinofsky; Bill Neukom (LCA)
Cc: John Mason (LCA)
Subject: FW: free desktop suite from star
Importance: Low
Attorney client privileged
An Interesting development...
[1]At some point we will have to consider the patents they violate. [gotthefacts.org]
[1] http://iowa.gotthefacts.org/011607/4000/PX04023.pdf
Any sensible institution would ... (Score:2)
Mandate an open file format so their data is not held to ransom.
Hint: Open Document formats are your friend and MS formats are the work of the devil.
Make your own standard if you don't like it (Score:2)
I had a coworker ~15 years ago who hated MS to the point he used OpenOffice even though the company provided a license of Office 200x. Invariably, we would need to share documents, presentations, and spreadsheets and all worked fine until he got sent a copy to update. Every single time he touch a doc and sent it to anyone, the formatting and other components would get off. He'd complain MS wasn't following the correct format for Word/Excel/PowerPoint.
When we told him the "format" for their tools is WHATEVER
That is just the default UI (Score:4, Informative)
LibreOffice has every single UI metaphor as a preset option to choose from. You can switch between hierarchical menus, tabbed ribbon menus, single and multi-line toolbars and a sidebar option akin to iWork. Try changing the UI to Tabbed if you prefer a Microsoft Office 2016 style of menu. They also added the compact tabbed mode similar to the compact ribbon introduced in 2021.
Re: That is just the default UI (Score:2)
Good to know - I'll give it a go
Re: (Score:2)
LibreOffice has had the option for a while now to switch to a ribbon-style layout if that's your thing. I've left it on the classic layout because IMO the ribbon's lack of customisability makes it less useful.
Re: less of a barrier than their terrible UI (Score:2)
Thanks for pointing this out, I'll give it a go
Re:less of a barrier than their terrible UI (Score:5, Insightful)
Do you think Office has a better UI then class LibreOffice? I guess that's an opinion, but in my opinion the Office UI is terrible, Microsoft is a master at terrible UI design. Compare Gnome / KDE / XFCE to the Windows desktop, and right away you notice Microsoft can't build a desktop. Another opinion, the Office 365 licensing is some form of a mix between intentional incompetence, weaponized incompetence, fraud, and a lack of requirements. The very fact that Office 365 can fail to activate on Windows 11, in some random cases, demonstrates the licensing is so broken, as to mitigate any attempt at producing an effective platform.
Have you tried to buy the right license for the right job? Microsoft has made it intentionally impossible, outside of luck, to pick the appropriate product, the first time. They have N tiers for the same tools, with intentionally misleading descriptions, no clarity on the differences, pricing that looks like a paint cannon went off, and if you try to get support, just shove a dry butt plug in your ass, it will hurt less. Do you want to get into the administration side? No, just no, I don't have the strength and mental energy right now.
Even if they did build Office 365 for Linux, it wouldn't matter. Office 365 is considered a train wreck of an Office platform, its name is used as a joke. The only reason people still use it, is because Microsoft forces it in your face during installs and updates, they even place download icons in the start menu. If Office 365 had to compete in the real world, on a fair playing field, no one would ever touch it.
I don't even have to bring up the terrible formats and extensions, they're bad, and are a universal symbol of the incompetent professional, but we don't even have to worry about that.
Re: (Score:2, Interesting)
> Do you think Office has a better UI then class LibreOffice? I guess that's an opinion, but in my opinion the Office UI is terrible, Microsoft is a master at terrible UI design.
Yep, same experience here. MS UIs do not aim to make users more efficient. MS intentionally (at least I have no doubt) makes UIs more cumbersome, slower, more clicks needed, because then users spend more time with that product and that, by an entirely perverted metric, makes MS more important.
This "success metric" can be found in one other place: Bureaucracies. Bureaucracies become more important (in their own view) if the can "bind" (i.e. waste) more time of others. MS uses the same disgusting and repulsiv
Re: less of a barrier than their terrible UI (Score:2)
> MS intentionally (at least I have no doubt) makes UIs more cumbersome, slower, more clicks needed, because then users spend more time with that product and that, by an entirely perverted metric, makes MS more important.
I'm going to call Hanlon's Razor* on this one. Over the years MS has layered new over old again and again instead of starting afresh that a lot of things are so convoluted as to be a right pain in the arse. Ever notice that the settings dialog box for a network adaptor looks remarkably like the 98/NT4 version? That's not a design choice. The root cause is laziness if you ask me; it's easier to preserve backwards compatibility if you plaster over the cracks than tearing down and rebuilding.
* Though I prefer
Re: (Score:2)
> MS UIs do not aim to make users more efficient. MS intentionally (at least I have no doubt) makes UIs more cumbersome, slower, more clicks needed, because then users spend more time with that product and that, by an entirely perverted metric, makes MS more important.
It's been a couple of decades since I used Office, but I occasionally watch her using it and the UI seems like an inefficient and confusing shit show. But she's so used to it that she doesn't like using LibreOffice. And TBH, I don't love their UI either. Then again, I don't use the product much.
> This "success metric" can be found in one other place: Bureaucracies. Bureaucracies become more important (in their own view) if the can "bind" (i.e. waste) more time of others. MS uses the same disgusting and repulsive model.
I haven't spent much time working at big companies, but I've been on the sidelines as the company my wife works for gets bigger and stupider. It seems that at about a hundred employees a company is really straining t
Re: (Score:2)
Microsoft is "interesting" when it comes to UI because they are both co-responsible for the dominant paradigm we all know and use and are used to and hey, actually works... and have gone to shit since.
Microsoft was part of the Motif WG, Motif implemented much of IBM's CUA, and to this day Windows and all popular Unix DEs both still do. But on the other hand, Microsoft's greatest independent contribution to UI remains the start menu, which isn't even something they really invented; its best-loved form (From
Preach it (Score:2)
I work for a startup made-good, bought by a very large company you have heard of if you live in the US.
The switched us to Office/Outlook about a year ago.
Shit still doesn't work.
My only use of word is to format docs for the business types after I write them, so I don't really care about it. I mean, it is shitty, but whatever, I'm a Unix guy, I'm used to shitty UI.
What does bug me is Outlook. I get invites to meetings after they happen, mail gets randomly delayed for no apparent reason while I get oth
Re: (Score:2)
I have a bug with one of my users, where she constantly gets kicked out of the Office Desktop applications, and runs into numerous activation errors. We don't know why, her system is configured effectively the same as everyone else, and she's running Windows 11 Pro, like everyone else, but just can't log into Office Desktop. She can log in to the Office Web Portal, so her license is active, but it just won't translate to the desktop.
Where this comes into UI issues, do you think the error is clearly exp
Re:less of a barrier than their terrible UI (Score:4, Interesting)
What? Working with LibreOffice is wayyyy more efficient than with MS Office. You actually find things and it does not take tons of clicks to do stuff. It does not permanently stand in your way. MS Office really has no chance in a direct comparison except with a few Stockholm Syndrome sufferers and these can still activate the stupid and cumbersome "ribbon" interface in LibreOffice as well.
And incidentally, LibreOffice, being derived from StarOffice has 40 years of development history. That is 5 years more (!) than MS Office.
Re: less of a barrier than their terrible UI (Score:2)
So LibreOffice is running 40 year-old code?
So LibreOffice developers have been with the proxy for 40 years?
That start date is really quite meaningless since the development team has likely turned over a few times and I'm certain the underlying software isn't based on anything from 40 years ago.
Microsoft has over 50 years in the computer industry, pre-dating LibreOffice by an easy decade.
MS Office was released in 1988, Star Office was released in 1985, but MS Word 1.0 shipped 1983 and MS Excel 1.0 in 1985 (f
Re: (Score:2)
Oh, my sweet summer child, OOXML is technically an ISO standard (Microsoft managed to get it approved as an ISO standard somehow, despite OOXML not adhering to ISO conventions in things such as dates and not having a reference implementation), which allows governments to upload docx files for citizens to use as forms and pretend they are issuing a standards-compliant file.
So, LibreOffice has to care about OOXML because governments issue OOXML files. You can choose to not interact with private individuals
Re: (Score:1)
I've been using LO pretty much constantly for the last two years (even wrote a novel on it). Like any interface, it just takes time to become familiar. In fact, I like the way Writer organizes styles and style configuration far better than Word, and often, even for DOCX files, do initial style set up and layout in Writer and then move to Word if I have to (which is seldom enough).
LO is a damned good office system. Its default UI is older, but since I used MS-Edit and Word pretty extensively back in the 1990