this post was submitted on 15 Aug 2025
182 points (99.5% liked)

Technology

74024 readers
1502 users here now

This is a most excellent place for technology news and articles.


Our Rules


  1. Follow the lemmy.world rules.
  2. Only tech related news or articles.
  3. Be excellent to each other!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
  9. Check for duplicates before posting, duplicates may be removed
  10. Accounts 7 days and younger will have their posts automatically removed.

Approved Bots


founded 2 years ago
MODERATORS
 
you are viewing a single comment's thread
view the rest of the comments
[โ€“] squirrel@lemmy.blahaj.zone 39 points 9 hours ago (1 children)

I remember when Microsoft first attempted to prevent the standardisation of Open Document Format (used by LibreOffice and others) and then bullied its way into getting approval for own OOXML standard. Already back then, supporters of FOSS warned that Microsoft would use the overly complicated OOXML to maintain its stranglehold on users of Office-like software.:

Whenever applicable and possible, standards should build upon previous standardisation efforts and not depend on proprietary, vendor-specific technologies. Albeit, MS-OOXML neglects various standards and uses its own vendor-specific formats instead. This puts a substantial burden on all vendors to fully implement MS-OOXML. It seems questionable how any third party could ever implement them equally well, especially when a standard comes with 6000 pages of specifications without serving its minimalistic purpose.

[โ€“] loutr@sh.itjust.works 27 points 8 hours ago

Yeah, the issue is not "Microsoft's usage of the XML format". The issue is that they blatantly bought their format's standardization, and then intentionally released an implementation that substantially deviated from the specs, making sure that MSO was the only "compatible" implementation.