That argument sits at the heart of a recent personal essay by tech writer Simon Batt on XDA Developers, chronicling how a decade-old skepticism toward open-source apps gave way to a full-blown migration in 2025. What began as an effort to keep an aging PC alive without upgrading to Windows 11 turned into a broader overhaul of his operating system, creative toolchain, and office suite—driven less by price tags than by trust. For Windows users watching hardware cutoffs, subscription price hikes, and private-equity buyout talks reshape familiar software, Batt's switch offers a timely case study in what open-source licensing actually buys you—and what it doesn't.
From Windows 10 End of Support to Fedora KDE
Batt's exit from Windows started with a dilemma that millions of PC owners now know intimately. Microsoft officially ended standard support for Windows 10 on October 14, 2025, cutting off free security fixes, feature updates, and technical assistance for mainstream Home and Pro users. Faced with an older machine that lacked the Trusted Platform Module (TPM) 2.0 hardware required by Windows 11, Batt opted to install Linux in 2025 rather than buy a new rig.
He eventually settled on a KDE spin of Fedora—a pairing that reflects how polished modern Linux desktops have become. Today, the Fedora Project elevates Fedora KDE Plasma Desktop alongside its flagship GNOME-based Workstation as primary desktop editions, giving former Windows users a familiar taskbar-and-start-menu layout backed by regular updates from both Fedora and KDE contributors. Batt notes that if either project takes a turn he dislikes, switching to another desktop environment or distribution costs nothing. He also points to Linux's driver model, where contributors can submit support for new or forgotten USB peripherals straight into the Linux kernel, allowing distributions that adopt recent kernels to benefit.
Still, veteran IT admins know that one writer's smooth daily driver is not a universal guarantee. Before wiping a Windows 10 partition in frustration, Windows users on supposedly "incompatible" hardware have a few crucial checks worth running first:
- Verify whether TPM 2.0 is just asleep: Microsoft notes that many PCs built over the past several years—and especially custom-built desktops—ship with TPM 2.0 hardware disabled in BIOS/UEFI by default. Checking
Settings > Update & Security > Windows Security > Device Securityor motherboard firmware settings can sometimes unlock Windows 11 eligibility without spending a dime. - Check Windows 10 Extended Security Updates (ESU): For eligible devices running Windows 10 version 22H2 (Home, Pro, Pro Education, or Workstations), Microsoft's Consumer ESU program provides critical and important security patches through October 12, 2027, buying breathing room to plan an orderly migration.
- Watch kernel and vendor gaps on Linux: Kernel-level hardware support does not materialize on every user's desktop the moment a patch is written; availability depends on which kernel branch a specific distribution ships and tests. Niche peripherals, proprietary RGB/audio utilities, and anti-cheat-protected games can still require workarounds or remain Windows-only.
Section summary: Microsoft's Windows 10 end-of-support cutoff and Windows 11's TPM 2.0 requirement pushed Batt onto Fedora KDE, where modular desktop choices and kernel-driven hardware support won him over. Windows users facing the same crossroads should confirm their firmware settings and ESU options before assuming a hardware or OS jump is mandatory.
The Unity Rollercoaster and What an Open License Really Buys
Interestingly, Batt says the spark behind his essay wasn't Microsoft at all—it was game engine maker Unity. Developers who build on Unity have endured a turbulent stretch over the past few years, beginning with the 2023 uproar over Unity's proposed Runtime Fee, which sought to charge studios per installation once games crossed specific download and revenue thresholds.
Here, precision matters. Following intense developer backlash, Unity leadership formally canceled the Runtime Fee for games on September 12, 2024, before any existing or new titles were ever charged under it. The company reverted to seat-based subscriptions, doubled Unity Personal's free revenue ceiling to $200,000, and shifted to predictable annual pricing adjustments—including a 5% price bump for Unity Pro and Enterprise plans starting January 12, 2026. Yet even after burying the fee, Unity's corporate future stayed in the headlines: in early November 2026, Reuters reported that Unity held confidential buyout discussions after being approached by private equity firm Silver Lake Partners (which already holds roughly 8% of Unity) and Saudi Arabia's Public Investment Fund (PIF) around a $25 billion valuation. Coming months after Silver Lake and PIF helped take Electronic Arts private in a $55 billion leveraged buyout, the talks remain unconfirmed and no deal is certain, but they rattled developers all over again.
That uncertainty drove Batt to double down on Godot, the open-source 2D and 3D game engine. Because Godot is distributed under the permissive MIT (Expat) license, anyone can inspect the code, modify it, and redistribute modified or unmodified builds—even commercially—as long as the copyright notice and license text travel with it. Just as importantly for studios, Godot's MIT terms do not dictate the license of games made with the engine; creators retain sole ownership of their work.
Does that mean Godot is magically immune to drama? Not quite. While the MIT license legally guarantees that no single corporation can revoke the existing codebase or retroactively slap royalties onto it, a legal right to fork code is not the same thing as a healthy, thriving fork. Keeping a modern graphics engine competitive across consoles, mobile platforms, and Windows DirectX/Vulkan pipelines takes dedicated contributors, steady funding, and coordinated governance—the role currently supported by the non-profit Godot Foundation.
Section summary: Unity's canceled Runtime Fee and reported November 2026 acquisition talks highlight why vendor governance anxiety pushes creators toward MIT-licensed alternatives like Godot. Open licensing protects the legal right to fork and reuse code, though long-term viability still hinges on active maintainers and community backing.
LibreOffice, DOCX Friction, and the Format Lock-In Debate
When it comes to everyday productivity, Batt points to LibreOffice not just as a free replacement for Microsoft 365, but as an ideological counterweight to ecosystem lock-in. He highlights LibreOffice's vocal campaign urging users to move away from Microsoft's default document formats—a campaign that intensified sharply in 2026.
In July 2026, The Document Foundation (TDF)—the non-profit behind LibreOffice—published a sharp critique authored by founding member Italo Vignoli targeting Microsoft's Office Open XML formats (DOCX, XLSX, and PPTX). TDF argued that despite nominal standardization, Microsoft's formats contain implementation quirks, font dependencies, and proprietary extensions that behave inconsistently outside Microsoft Office. Vignoli characterized those subtle shifts in tables, bullets, and pagination as a "silent and persistent friction" that makes third-party suites look unreliable and keeps businesses and governments tethered to Microsoft's ecosystem. In response, TDF champions the ISO-standardized Open Document Format (ODF—.odt, .ods, .odp), designed so any vendor can implement full read/write support without undocumented surprises.
LibreOffice has also continued advancing on technical merits—such as its LibreOffice 26.8 release under the Mozilla Public License v2, operating without subscriptions, ads, or user telemetry. Still, Windows administrators and hybrid teams shouldn't confuse philosophical clarity with painless migration. LibreOffice's position represents one side of an ongoing standards debate, and anyone exchanging complex files with corporate clients, law firms, or SharePoint/Teams environments knows that real-world compatibility cuts both ways.
Before committing a department—or even your own home office—to an open-source suite, test representative files end-to-end:
- Run round-trip formatting checks: Open your gnarliest
.docxand.xlsxfiles in LibreOffice, edit them, save them, and reopen them in Microsoft Word or Excel to verify tables, headers, and pagination. - Audit macros and automation: VBA macros and legacy Excel formulas frequently break or require rewriting when moved out of Microsoft Office.
- Check collaboration workflows: Real-time co-authoring, tracked changes, and Microsoft Purview sensitivity labels rely heavily on Microsoft 365 cloud plumbing rather than just file extensions.
Section summary: Batt's enthusiasm for LibreOffice aligns with The Document Foundation's 2026 push against DOCX lock-in in favor of ODF. While open standards protect long-term document portability, Windows users working in mixed environments should still test complex templates and collaboration workflows before cutting ties.
Trust, Transparency, and Realistic Trade-Offs
At its core, Batt's essay reframes open-source software as a question of trust rather than cost. When proprietary software vendors pivot toward recurring subscriptions, cloud accounts, and shareholder-driven feature changes, transparent codebases governed by communities offer peace of mind.
From an objective cybersecurity and IT engineering standpoint, however, it is vital to separate governance trust from security guarantees. As the Linux Foundation emphasizes in its licensing and security guidance, open-source licenses almost universally disclaim warranties—meaning users run the software at their own risk. Openly readable source code makes independent inspection possible, yet welcoming public contributions does not automatically guarantee higher code quality, nor does it mean every open-source dependency is actively audited or patched promptly. Supply-chain vulnerabilities and stale libraries affect open-source projects just as bugs affect closed-source giants, which is why enterprises and savvy users look for explicit SECURITY.md disclosure policies, active release cadences, and OpenSSF best practices rather than trusting an "open-source" label blindly.
| Factor | Proprietary Ecosystems (e.g., Windows, Microsoft 365, Unity) | Open-Source Ecosystems (e.g., Fedora KDE, LibreOffice, Godot) |
|---|---|---|
| Control & Roadmap | Dictated by vendor priorities, M&A activity, or pricing shifts | Shaped by maintainers and foundations; forkable if governance splits |
| Licensing & Cost | Paid seats, revenue tiers, or hardware OS gates (e.g., TPM 2.0) | Free to use, inspect, and modify under licenses like MIT or MPL v2 |
| Compatibility | Native industry default for DOCX, enterprise MDM, and commercial apps | Strong open-standard support (ODF), though niche proprietary edge cases vary |
| Security & Support | Centralized vendor SLAs, formal patches, and ESU lifecycles | Community/foundation channels; quality depends on active maintenance |
The Bottom Line for Windows Users
You don't have to abandon Windows tomorrow—or wipe your SSD for Fedora—to take the best lesson from Batt's migration. Open-source software has matured well past the era when choosing free tools meant settling for second-rate compromises. Whether you stick with Windows 11 on compliant hardware, lean on Windows 10 ESU to buy transition time, or spin up Linux on an older PC, mixing open-source applications like LibreOffice or Godot into your Windows workflow is one of the easiest ways to reduce vendor dependency without upending your whole desk.
Just go in with your eyes open. Evaluate each tool on hardware support, active security maintenance, document round-tripping, and real support expectations—because true digital independence isn't about picking a team; it's about making sure your tools still work for you even if a corporation changes the rules.
References
- I moved to open-source software, and I trust my tools more than ever XDA · 2026-11-21T22:30:20+00:00
- Unity is Canceling the Runtime Fee unity.com
- Unity Pricing Changes | Unity unity.com