When did this happen?
I’ve been using Windows since version 3.1. That’s not a flex; it’s just context. I remember when an operating system’s job was refreshingly simple: boot up, run your programs, stay out of the way. Windows 95 felt like magic back then. Windows XP was rock solid for years. Even Windows 7, which many of us clung to like a life raft, understood the assignment.
Somewhere along the line, that changed.
I can’t pinpoint the exact moment, but I know the feeling. You sit down at your machine to get some actual work done, and Windows has other plans. There’s a notification about Microsoft 365 features you’re not using. The Start menu is suggesting apps you never asked for. Edge wants to be your default browser again, even though you’ve declined seventeen times. The widgets panel is showing you celebrity gossip and clickbait headlines because apparently that’s what a professional workstation needs.
This isn’t about hating Microsoft. I honestly think VS Code is brilliant. The Windows Subsystem for Linux genuinely changed my workflow for the better. But there’s a growing disconnect between what Windows could be and what it’s actively choosing to become. After spending the better part of 2025 helping teams migrate infrastructure and watching colleagues finally make the jump to Linux, I think it’s time to say the quiet part out loud: modern Windows behaves less like an operating system and more like a monetization funnel that happens to run your applications.
Let me show you what I mean.
The patterns: specific friction, not vague complaints
It’s easy to dismiss criticism of Windows as nostalgic whining. “Things change, old man. Deal with it.” Fair enough. But the frustration isn’t about change itself. It’s about the direction of change and who it benefits.
Let’s get specific.
The Start Menu as advertising space
Open the Start menu on a fresh Windows 11 installation in late 2024 or 2025. What do you see? Pinned apps you didn’t pin. Suggestions for games you didn’t ask for. Promoted applications that Microsoft gets paid to put there. The Start menu, which should be the most utilitarian part of your desktop, has become real estate that Microsoft monetizes.
Yes, you can remove these. Yes, you can disable suggestions. But why are they there by default? The answer is obvious: because the default state benefits Microsoft’s bottom line, not your productivity.
The Browser Wars, 2025 edition
Try setting Firefox or Vivaldi as your default browser. Actually, try it right now if you’re on Windows. Notice how the process involves multiple clicks, a settings page that doesn’t make the option obvious, and sometimes a friendly little prompt asking if you’re really sure you don’t want to try Edge. Microsoft has made this process deliberately friction-heavy.
Earlier this year, the EU forced Microsoft to add a proper browser choice screen for European users under the Digital Markets Act. The fact that it took regulatory intervention to get a straightforward “pick your browser” prompt tells you everything about Microsoft’s priorities.
Widgets: the panel nobody asked for
The widgets panel, pinned to your taskbar by default, is essentially MSN.com repackaged as a system feature. Weather is useful from time to time, sure. But the rest? It’s a news feed algorithmically tuned for engagement, which in practice means sensationalized headlines and content designed to make you click, not content designed to inform you.
For a developer or knowledge worker trying to focus, this is hostile by design. It’s a distraction engine built into your operating system. You can disable it, but it often re-enables itself after major updates. More on that problem shortly.
The Microsoft account push
Setting up a new Windows 11 machine without a Microsoft account has become an exercise in determination. Microsoft really, really wants you to sign in. The prompts are persistent. The “offline account” option is buried or, depending on your Windows edition, requires workarounds that feel deliberately obfuscated.
Why does Microsoft care so much? Because a Microsoft account means they can tie your activity across services, serve you more relevant ads, and lock you deeper into the ecosystem. It’s rational from their perspective. It’s just not great for users who want local accounts and less data collection.
Settings that betray you
Privacy settings in Windows are a maze, and the defaults are not privacy-respecting. Diagnostic data, advertising ID, tailored experiences, location tracking… all enabled by default. You can turn them off, but you need to know they exist and where to find them.
And here’s the part that really gets me: these settings sometimes reset after feature updates. You did the work, you configured your system, and then a Windows update comes along and decides some of those choices need revisiting. This is the “settings drift” problem, and it’s not a bug. It’s a feature of a system designed to maximize engagement and data collection.
Why “just debloat it once” doesn’t work anymore
I used to give this advice. Run a PowerShell script, remove the bloatware, disable the telemetry, configure your privacy settings, and you’re golden. Set it and forget it.
That advice has an expiration date now.
Windows updates, especially the big feature updates that roll out once or twice a year, have a habit of undoing your work. Apps you removed get reinstalled. Settings you changed get reverted. The browser default prompt comes back. It’s like playing whack-a-mole with your own operating system.
This creates a maintenance burden that simply didn’t exist five or ten years ago. Your operating system is supposed to be infrastructure, the stable foundation you build your work on. When that foundation requires constant vigilance and re-configuration, something has gone fundamentally wrong with the relationship between vendor and user.
Some folks in the IT community have built elaborate deployment scripts and used tools like group policy editors to lock things down. That works for enterprise environments with dedicated sysadmins. For individual developers, freelancers, or small teams? It’s exhausting. You shouldn’t need a degree in Windows administration to have a focused, ad-free computing experience.
The truth is, Microsoft has no incentive to make this easier. Every promoted app you see, every Edge prompt you click through, every moment you spend in the widgets panel represents potential revenue. The friction is the feature.
Switching as an engineering decision
Here’s where I want to shift the tone from complaining to practical thinking.
Choosing an operating system is an engineering decision. Like any engineering decision, it involves trade-offs. Emotional attachment, familiarity, and sunk cost shouldn’t be the primary factors. What matters is whether the tool serves your needs effectively and sustainably.
So let’s think through this properly.
When staying on Windows makes sense
Windows is still the right (sometimes – the only) choice for some people:
- Gaming: If you’re a serious PC gamer, Windows may still remain your best option. Steam’s Proton compatibility layer has made Linux gaming surprisingly viable, but Windows is still where you get the smoothest experience with the latest titles, the best driver support, and zero compatibility headaches (mostly because of hardware manufactures not interested in supporting an OS which isn’t as mainstream).
- Specific professional aoftware: If your work depends on Adobe Creative Suite, certain CAD applications, or industry-specific tools that only run on Windows, switching isn’t practical. Compatibility layers and VMs can work, but they add friction to workflows that need to be seamless.
- Enterprise environments: If your company runs on Active Directory, Microsoft 365 with heavy SharePoint/Teams integration, and Windows-specific management tools, you’re in the Microsoft ecosystem whether you like it or not. Fighting that fight as an individual employee usually isn’t worth the energy.
- Hardware compatibility concerns: If you’re running specialized hardware with drivers that only exist for Windows, that’s a real constraint.
When Switching Pays Off
On the other hand, switching becomes increasingly rational when:
- Your work lives in the browser and terminal: If you’re a web developer, a DevOps engineer, or anyone whose primary tools are browser-based apps, VS Code, and command-line utilities, you don’t actually need Windows. These workflows translate almost perfectly to Linux or macOS.
- You value privacy and control: If the telemetry, ads, and constant nudging genuinely bother you, and it’s okay if they don’t, then switching removes the problem at the source rather than fighting it endlessly.
- You want predictability: Linux and macOS don’t randomly reinstall apps or reset your preferences after updates. What you configure stays configured. This predictability has real value for focus and productivity.
- You’re tired of the Maintenance Tax: If you’re spending hours every few months re-debloating your Windows installation, that’s time you could spend on actual work. At some point, the migration cost is less than the ongoing maintenance cost.
The macOS option
I’d be remiss not to mention macOS. If you’re in a financial position to buy Apple hardware and your workflows don’t depend on Windows-specific software, macOS is a genuinely excellent Unix-based operating system with strong privacy defaults and a polished user experience.
The caveats are real: Apple hardware is expensive, repairability is limited, and you’re trading one corporate ecosystem for another. But Apple’s business model is primarily hardware sales, not advertising, which means the incentives around user experience are different.
For developers specifically, macOS gives you a proper Unix terminal, excellent build tooling, and wide compatibility with deployment targets that are usually Linux servers anyway.
Linux in 2025: what’s actually better now
Okay, let’s talk about the penguin in the room.
Five years ago, recommending Linux as a daily driver for anyone but enthusiasts felt irresponsible. There were too many sharp edges, too many “just compile it from source” moments, too many hardware compatibility nightmares.
That’s changed meaningfully. Not completely, but meaningfully.
What’s genuinely easier
Hardware support has improved dramatically. Modern distributions like Ubuntu 24.04, Fedora 41, and Linux Mint 22 work out of the box on most mainstream laptops. WiFi, Bluetooth, suspend/resume, display scaling… these things generally just work now on common hardware. The days of spending a weekend getting your wireless card recognized are largely behind us for mainstream devices.
Installation is straightforward. Seriously, installing Ubuntu or Fedora is easier than installing Windows at this point. The installers are clean, the process takes maybe 15 minutes, and you end up with a working system including a browser, office suite, and basic productivity tools.
Gaming has come way further than anyone expected. Steam’s Proton compatibility layer, built on Wine and a lot of Valve engineering, lets you play a huge percentage of Windows games on Linux without configuration. Check ProtonDB before you switch to verify your specific games, but for most people, Linux gaming is now practical rather than theoretical.
Flatpak and Snap have simplified software installation. You don’t need to worry about dependency hell or finding the right repository for common applications. Discord, Spotify, Slack, Zoom… they’re all available as Flatpaks that install with a click.
The desktop environments have matured. GNOME and KDE Plasma are polished, modern, and visually competitive with Windows and macOS. This matters because the “Linux looks like it’s from 2003" criticism used to be valid. It really isn’t anymore.
What still bites
I’m not going to pretend Linux is perfect. Honesty serves you better than cheerleading.
Nvidia graphics can still be painful. AMD and Intel integrated graphics work beautifully with open-source drivers. Nvidia requires proprietary drivers that sometimes conflict with kernel updates. This is getting better, slowly, but if you have an Nvidia GPU, research your specific card’s compatibility before committing.
Some professional software simply doesn’t exist. No native Adobe Creative Cloud. No native Microsoft Office (the web versions work, but it’s not the same; I love the alternatives, but not everyone will). If these are non-negotiable for your work, Linux isn’t your answer, or you’ll need to run Windows in a VM for those specific tasks.
Peripheral support varies. That fancy gaming mouse with twelve buttons? The software to configure it might be Windows-only. Webcams, drawing tablets, and specialized hardware sometimes require hunting for community drivers or alternative configuration tools.
The “just Google it” problem. When something goes wrong on Linux, fixing it often involves terminal commands and reading forum posts. The knowledge is out there, but it’s often not as point-and-click as Windows troubleshooting tends to be.
Corporate IT support is usually nonexistent. If you’re in a company that provides tech support for employees, they probably don’t support Linux. You’re on your own.
The honest trade-off
Here’s my take, and it’s just my take.
If you’re technical enough to be reading this article, you’re technical enough to run Linux. The learning curve exists but it’s not steep for someone who’s comfortable with a terminal. You’ll spend some time upfront learning new tools and workflows, and then you’ll have an operating system that respects your attention, doesn’t serve you ads, doesn’t nag you about browsers, and stays configured the way you left it.
For me, that trade was worth it. I switched my personal machines to Garuda and Ultramarine (Fedora’s derivative) two years ago and haven’t looked back. My work machine is still Windows because that’s what the client environments require, and I notice the difference every single day. One system works for me. The other system works for Microsoft first and me second.
Your mileage will vary. Your needs are different. That’s fine.
What’s coming next
This article is deliberately high-level. I’ve tried to make an argument and provide a framework for thinking, not a step-by-step migration guide.
That guide is coming.
In one of the upcoming articles, I’ll get specific about Linux distributions: which ones are genuinely beginner-friendly, which ones make sense for developers, and which ones are worth considering if you have specific needs like gaming or creative work. I’ll also walk through a practical migration path that minimizes pain, covering how to back up properly, how to handle your browser profiles and password managers, and how to identify your “must-have” applications before you commit.
If you’ve been Windows-curious about Linux, or if this article has you thinking seriously about making a change, that piece will give you the concrete next steps.
Modern Windows isn’t broken. It runs your apps. It’s stable enough. It gets the job done.
But “gets the job done” is a low bar for something you interact with eight or more hours a day. An operating system should be infrastructure, quiet and reliable and working in your interest. When it becomes a surface that competes for your attention, serves you ads, pushes you toward services, and resets your preferences when you’re not looking… that’s a different relationship. That’s a product that views you as the product.
You don’t have to accept that. Alternatives exist, and they’re more viable now than they’ve ever been.
I’m not telling you to switch. I’m telling you that switching is a legitimate option worth evaluating on its merits. Make the decision that serves your work, your values, and your sanity.
And if you do decide to explore Linux, I’ll see you soon in another article.
Got thoughts on this? Made the switch yourself, or decided to stay? I’d love to hear what your experience has been. Drop a comment below or find me on Mastodon. And if you want the follow-up guide on choosing a Linux distribution, make sure you’re subscribed so you don’t miss it.