Why Engineers Are Ditching Windows: The Great Desktop Migration
TL;DR
Windows has become hostile to power users. Between aggressive telemetry, mandatory Microsoft accounts, arbitrary hardware requirements that obsolete 500M PCs, and ads baked into the OS, Microsoft is bleeding users to Linux. Governments in Germany, France, and Denmark are migrating tens of thousands of systems. Desktop Linux hit 5% US market share in 2025, a historic milestone. But here’s the catch: most engineers still can’t switch because Adobe won’t ship for Linux, kernel-level anti-cheat blocks gamers, and enterprise tooling requires Windows. This is the story of why we’re trapped, why some are escaping, and what it means for the next decade of desktop computing.
Why I Left Windows (and You Probably Should Too)
I ditched Windows for Linux Mint last year. The reasons were prosaic but cumulative:
- RAM bloat: Windows 11 idling at ~16GB with 20 browser tabs. Same workload on Mint: ~9GB.
- Installation friction: Everything on Windows needs an installer, a reboot, and three confirmation dialogs. On Linux:
apt installand you’re done. - Docker’s VM tax: Running Docker Desktop on Windows means running a VM. On Linux, containers are native.
- Forced ads: My Start menu advertises Microsoft 365. I paid for this OS.
- Minimal customization: Want to change how window tiling works? Good luck.
Gaming improved dramatically (Steam + Proton handles 80% of my library). Office work moved to Google Docs and LibreOffice.
That said, I chose Mint over Ubuntu after Ubuntu corrupted my login three separate times and nuked my home directory (probably my mistake but Mint have been forgiving so far). Always have backups. Always.
The Windows 7 → 10 Migration: When Users Started Saying No
Windows 7 remains beloved because it didn’t spy on you, didn’t force updates, and ran on anything. Windows 10 broke all three promises.
Telemetry: The Privacy Implosion
Windows 10 shipped with Compatibility Telemetry enabled by default, collecting device configs, software usage, performance metrics, and behavioral data. Unlike 7’s opt-in diagnostics, Windows 10 made opting out deliberately obscure. The tech press called it surveillance. Microsoft called it “improving the user experience.”
Disabling telemetry required registry hacks, Group Policy changes, and third-party tools. For most users, it was easier to just accept that their OS was now phoning home 24/7.
Forced Updates That Delete Your Files
Windows 10 made updates mandatory. No postpone button. No “remind me later.” If Microsoft pushed an update, your machine rebooted whether you wanted it or not.
The October 2018 Update famously deleted user files. Not some files, entire user accounts vanished. Microsoft pulled the update, but the damage was done: users realized “stable” was no longer guaranteed.
The Trust Deficit
Windows 7 users saw Windows 10 as a downgrade: more resource-hungry, less private, less stable. Many refused to upgrade until security patches ended in 2020, and even then, some stayed behind.
Windows 11: When Microsoft Stopped Pretending to Care
If Windows 10 was a warning shot, Windows 11 is full siege mode. 500 million PCs that can run Windows 11 haven’t upgraded, not because they can’t, but because users actively refuse. And for good reason: Windows 11 consumes 50% CPU and 30% RAM at idle without any user applications running. Background telemetry, indexing, widget feeds, and Microsoft Store pre-loaders chew resources nonstop. People preferred Windows 8, the biggest failure in Windows history, over 11.
But performance is the least of Windows 11’s sins. The OS now serves ads in the Start menu you paid $200 for. “Suggested apps” promote Microsoft services. Fresh installs come with Candy Crush, trial antivirus, and promotional bloatware. Why does a premium OS behave like adware?
Worse still, Windows 11 Home and Pro now require a Microsoft account during installation. The “create local account” option was removed. Workarounds existed (OOBE\BYPASSNRO, start ms-cxh:localonly), but Microsoft keeps patching them out. Current builds require registry hacks or third-party tools like Rufus to bypass the requirement. Why? Because Microsoft wants your data, your email, and to lock you into their cloud ecosystem.
The TPM 2.0 Catastrophe: 500 Million PCs Obsoleted Overnight
Microsoft’s most destructive decision: Windows 11 requires TPM 2.0, 8th-gen Intel CPUs (or Ryzen 2000+), and UEFI Secure Boot. These aren’t security features, they’re planned obsolescence.
The damage:
- 500 million functional PCs cannot run Windows 11
- Only 57% of existing PCs meet CPU requirements
- Only 75% have TPM 2.0 chips
What this means: Enterprises with 10,000-PC fleets must replace 40-50% of their hardware not because it’s slow, but because Microsoft said so.
The E-Waste Apocalypse
Windows 10 support ends October 14, 2025. Microsoft’s answer: “Buy new hardware or pay us for extended support.”
Estimated fallout:
- 240-400 million PCs destined for landfills
- 700 million kg of e-waste
- Right to Repair groups call it “the largest case of premature, planned obsolescence in history”
Microsoft offers Extended Security Updates (ESU), but now requires a Microsoft account to purchase them. Offline business PCs? Too bad.
Windows Recall: The AI Surveillance Nightmare
Microsoft’s Copilot+ PCs ship with Recall, a feature that screenshots your desktop every 3 seconds, OCRs the content, and builds a searchable AI index of everything you’ve ever seen.
Security researchers went ballistic:
- Every message in Signal, every password entry, every private document gets indexed
- The database is a “treasure trove for malicious insiders, criminals, or state-sponsored spies”
- Even if you disable Recall, anyone you message who has it enabled will archive your conversation
Signal added a “Screen Security” setting to block Recall. Microsoft’s response? Silence.
This is the future Microsoft wants: your OS as a surveillance appliance.
Governments Fleeing to Linux
Europe is done with Microsoft’s BS. Germany’s Schleswig-Holstein state is migrating 60,000 civil servants and 30,000 teachers off Microsoft entirely: Windows → Linux (KDE Plasma), Office → LibreOffice, Outlook → Open-Xchange, Teams → anything else. Minister Dirk Schrödter summed it up: “We’re done with Teams!” The rationale is digital sovereignty, Germany refuses to let US tech companies control government data.
France went further. The National Gendarmerie has run GendBuntu (custom Ubuntu) since the early 2000s. As of 2024, 97% of workstations (103,000+ PCs) are Linux. It works. It’s been working for 20+ years. Denmark’s Ministry of Digital Affairs joined the exodus, citing a stark concern: “If we can’t send emails because of a political fallout with the US, that’s a massive problem.”
A petition for “EU-Linux” now calls for the European Union to develop and deploy a standardized Linux distribution across all member states. It’s gaining traction as geopolitical tensions with US tech giants escalate.
Linux Market Share: The 5% Milestone
Desktop Linux hit 5.03% market share in the US (June 2025), a historic achievement. Add ChromeOS (also Linux), and the Linux family reaches 7.74%. The growth trajectory is undeniable: 1.5% in 2020, 2% in 2021, 3.12% in 2023, 4%+ in 2024, and now 5%+ in 2025.
Three forces converged to make this happen: Steam Deck (Valve’s Linux-powered handheld normalized Linux gaming for millions), Proton maturity (AAA titles now run on Linux without dual-booting), and Windows hostility (forced accounts, telemetry, and planned obsolescence finally broke user patience).
But desktop Linux is only part of the story. Where Linux truly dominates is servers, data centers, and AI infrastructure, the computing that actually powers the modern world.
Linux Already Won: Servers, AI, and the Infrastructure
While the desktop wars rage on, Linux has already won where it matters: the infrastructure running the internet, cloud computing, and AI. The numbers are absurd:
- 96.3% of the top one million web servers run Linux
- 90% of cloud infrastructure (AWS, Azure, Google Cloud) runs on Linux
- 91.5% of the world’s top 500 supercomputers run Linux
- 78.3% of all web-facing servers run Linux
- Among Fortune 500 companies, 72.6% run mission-critical workloads on Linux
Why the total dominance? Cost (zero licensing fees for thousands of servers), stability (Linux servers run for years without reboots, decades in some cases), security (open-source transparency allows rapid patching), and scalability (Linux handles massive distributed workloads better than anything else). Enterprises running 10,000-server data centers save millions annually by avoiding Windows Server licensing costs.
Even Microsoft admits defeat: Azure runs more Linux VMs than Windows VMs. Their own cloud infrastructure relies on Linux.
NVIDIA’s Linux Strategy: Follow the Money
Here’s the dirty secret desktop Linux users don’t want to hear: NVIDIA prioritizes Linux, just not for US. Approximately 89% of NVIDIA’s revenue comes from data centers, not gaming (which is only 8.7% of revenue). NVIDIA’s actual engineering investment goes into Linux support for AI and HPC workloads, not desktop gamers.
In enterprise data centers, NVIDIA’s Linux support is exceptional:
- CUDA is optimized primarily for Linux servers
- NVIDIA’s container toolkit is “the most reliable way to get GPU acceleration on any OS”
- Enterprise GPUs ship with drivers designed for Red Hat Enterprise Linux
- Many NVIDIA servers ship with DGX OS (a custom Ubuntu variant)
Desktop Linux gamers complaining about driver quality are missing the point: supporting 273 different Linux distributions for desktop gaming would be enormously expensive for maybe 3-5% of NVIDIA’s gaming revenue. It’s a rounding error. Meanwhile, NVIDIA has invested billions into Linux support for AI infrastructure because that’s where the actual money is.
Large language model training, the most computationally intensive work on Earth, runs almost exclusively on Linux. When Meta trains LLaMA 3 on 16,000+ GPUs across 2,000+ nodes, they use:
- Linux-based GPU nodes (NVIDIA H100 or A100 accelerators)
- Docker and Kubernetes (Linux-native containerization)
- InfiniBand networks for GPU-to-GPU communication
- Hierarchical checkpointing to prevent training failures
Windows cannot do this. Training jobs that last weeks cannot afford forced reboots. AI frameworks (TensorFlow, PyTorch, Scikit-Learn) were all built with Linux as the primary target. Ubuntu dominates AI infrastructure because of built-in CUDA support, seamless Docker integration, and a massive community of ML engineers.
Even developers using Windows locally deploy to Linux servers. The pattern is universal: develop on Windows or macOS, train and deploy on Linux. The entire AI revolution, ChatGPT, Stable Diffusion, autonomous vehicles, drug discovery, runs on Linux infrastructure.
Why Most Engineers Still Can’t Switch
Here’s the brutal truth: Linux has fatal gaps that keep most professionals locked into Windows.
The single biggest blocker: Adobe Creative Cloud does not run on Linux. Period.
Photoshop, Premiere Pro, After Effects, Illustrator, these are non-negotiable tools for filmmakers, designers, and video editors. Adobe actively blocks Linux (their installers detect the OS and refuse to proceed).
Wine and Proton don’t cut it for production work. If you’re a professional creative, you’re stuck on Windows or macOS.
As for Gamers, while Proton fixed most gaming compatibility issues, kernel-level anti-cheat systems actively ban Linux users.
Games that don’t work on Linux:
- Valorant
- Fortnite
- League of Legends
- Lost Ark
- Destiny 2 (deliberately disabled Linux support despite EAC technically supporting it)
The technical support exists (EAC and BattlEye have Linux builds), but publishers choose to disable Linux. This is a business decision, not a technical limitation.
While for organizations, migrating a 10,000-employee organization off Windows means:
- Rewriting or replacing mission-critical internal apps
- Retraining staff
- Rebuilding authentication and policy management infrastructure
- Potentially losing regulatory compliance
Cost: millions of dollars. Risk: catastrophic. ROI: unclear.
Adding to all of it the Learning Curve and Toxicity Tax. Linux requires understanding concepts Windows hides: what a distribution is and which one to choose (273 active distros!), why your Wi-Fi card needs proprietary firmware, how package managers work, when you need to edit /etc/fstab or recompile a kernel module. Windows abstracts this. Linux makes you deal with it.
Even developers report spending hours troubleshooting printer drivers, audio pipelines (PulseAudio vs. PipeWire), and display server issues (X11 vs. Wayland). And when you ask for help on Linux forums, you’ll often get “RTFM,” “sounds like a skill issue,” or ideological gatekeeping about systemd, GNOME, or Red Hat. When newcomers encounter problems and receive hostile responses, they leave permanently. This cultural barrier is as significant as any technical one.
Final Thoughts
If you’re an individual developer or power user:
- Try Linux Mint or Pop!_OS in a VM. Test your workflow.
- Check if your games work on ProtonDB.
- If you need Adobe, you’re stuck, but consider alternatives (DaVinci Resolve, Affinity, Figma).
If you’re an engineering manager or CTO:
- Audit how many Windows-only tools you actually need. Many have Linux replacements.
- Consider a hybrid approach: dev teams on Linux, creative/business teams on Windows.
- Budget for ESU if you can’t upgrade hardware, but know Microsoft will keep raising prices.
If you’re a government or large enterprise:
- Digital sovereignty is real. Dependence on US vendors creates geopolitical risk.
- Linux migrations are expensive upfront but eliminate licensing costs forever.
- France’s Gendarmerie and Germany’s Schleswig-Holstein prove it scales.
Continue reading
Next article
P99
Related Content
TLS: How Your Browser Keeps Secrets (And Why It's Harder Than You Think)
A no-bullshit deep dive into TLS 1.3: the handshake, record protocol, certificate chains, and why perfect forward secrecy actually matters. With annotated diagrams because the RFCs are 100+ pages.
Clean Code: The Cult of Dogma and Why Your Abstractions Are Probably Wrong
Robert C. Martin's Clean Code shaped a generation of developers, but its dogmatic rules about tiny functions, obsessive DRY, and terrible example code have caused more harm than good. Here's what the book got right, what it got catastrophically wrong, and what to read instead.
Pragmatic Clean Code: The Full Guide to Ownership & Entropy
Stop making excuses and start fighting software entropy. A senior engineer's guide to the Broken Window Theory, negotiating technical debt, and treating your knowledge like an investment portfolio.