How proprietary formats have become Microsoft’s main tool for lock-in
Microsoft’s reliance on proprietary document formats and tightly integrated cloud services is widely seen as a key mechanism for locking organizations into its ecosystem, from Office and OneDrive to Azure and Entra. Commenters contrast this with open standards like OpenDocument and PDF, arguing that governments and public institutions in particular should mandate truly interoperable formats to avoid long-term dependency and migration costs. Others counter that format lock-in is only part of the story, pointing to Microsoft’s bundle of email, identity, admin tooling, and aggressive enterprise sales tactics as the deeper reason competitors and open-source alternatives struggle to gain ground.
Onedrive, Accounts, and Usability
- Several users describe OneDrive as unreliable: failed large-folder downloads, inconsistent sync status between tray icon, Explorer, and web UI, and no easy way to verify full sync.
- External sharing often forces recipients into Microsoft accounts and app-based authentication; others note this is usually an org policy, and that anonymous links and non-Microsoft OTP apps or SMS can work if configured.
- Outlook’s UX is criticized for nudging users into OneDrive links instead of real attachments, further entrenching the ecosystem.
Proprietary Formats and Lock‑In
- Many see Microsoft’s proprietary formats (especially OOXML variants) as a core lock‑in mechanism, particularly around PowerPoint and complex Office documents that break in alternative suites.
- Others argue proprietary formats are the industry norm and a “natural” result of serializing unique feature sets; the real competitive edge is full platform integration (email, identity, storage, admin tools), not just formats.
Government Use and Open Standards
- Some advocate for mandates that all government documents be stored and published in open, standardized formats (ODF, PDF, text), with transitional use of more open subsets of OOXML if necessary.
- There is debate over whether real-world government workflows can quickly abandon legacy Microsoft formats given existing processes and dependencies.
Cloud Tools vs File Formats
- One camp says focus on “file formats” is outdated because cloud/browser suites dominate, though others counter that cloud services can make lock‑in even worse and migration harder.
- OpenDocument is cited as a solid ISO standard that works well in practice; skepticism remains about whether standards alone solve interoperability.
Interoperability and Technical Difficulty
- Multiple comments stress that truly faithful import/export requires reproducing Microsoft’s rendering and even bugs; specs are often incomplete, and “the code is the real spec.”
- Examples given: font rendering, layout differences, PDF quirks, and the general challenge of bug‑for‑bug compatibility across complex formats.
LibreOffice, Funding, and Competing Suites
- Some criticize LibreOffice and its stewards for focusing messaging on attacking OOXML instead of delivering feature parity, citing underfunding and weaker integration versus Microsoft or Google.
- Others report success with alternative suites (e.g., kSuite, ONLYOFFICE, Euro‑Office) but still hit edge‑case incompatibilities that make organizations default back to Microsoft.
Linux Desktop and Ecosystem Issues
- Office is described as a major but not sole blocker for desktop Linux adoption; other obstacles include OEM support, gaming, government/legacy software, and heavy ecosystem fragmentation and churn.
- Long‑time open source contributors argue that frequent backward‑incompatible changes make Linux a difficult target for third‑party desktop software.
LLMs and Reverse Engineering
- Commenters report using LLMs to reverse engineer legacy proprietary formats (e.g., old CorelDraw) when open-source libraries failed, and suggest LLMs can now power near‑pixel‑accurate read‑only viewers for Office files.
- Tools like Ghidra‑based workflows are mentioned as promising for reverse engineering complex binary formats, though details are sparse.