There is a quiet war happening in tech right now.
Not the dramatic kind you see in headlines. Not the kind companies openly admit. It is slower than that. More boring. More corporate. And that is exactly why it works.
It is the gradual movement toward closed, controlled, locked-down platforms where you buy the device, but someone else controls the rules.
You own the hardware.
But do you really own the experience?
That is the uncomfortable question.
For years we were told that every new restriction was for our own good. More security. More privacy. More protection from malware. More protection from ourselves.
And sure, some of that is true. I am not going to pretend that the old wild-west model was perfect. Old computers were messy. People installed random EXE files, broke system folders, destroyed Windows installations, and then blamed the machine.
But we also had something important back then.
We had control.
We did not lose that control overnight. We lost it update by update. Permission prompt by permission prompt. Store policy by store policy. Hardware generation by hardware generation.
And now most people do not even notice it anymore.
That is the scary part.
When the Computer Was Actually Yours
There was a time when buying a computer meant something simple.
You bought the machine, and it was yours.
You could install the operating system you wanted. You could install an older version if you preferred it. You could open the machine, replace parts, boot from whatever media you had, modify system files, install unsigned software, and generally treat the computer like a real tool.
Yes, you could break things.
But that was part of the deal.
If you messed up the system, you restored from a backup, reinstalled the OS, or fixed it manually. It was annoying, but it was also honest. The computer did what you told it to do. Sometimes that was a bad idea, but at least the decision was yours.
For many of us, the important milestones looked something like this:
- Windows XP
- macOS Snow Leopard
- Early Android
- Classic desktop Linux
- Old ThinkPads, old MacBooks, old beige boxes, and random PC builds
Those systems were not perfect. They were buggy, insecure, inconsistent, and sometimes ugly.
But they were powerful.
If you wanted to install unsigned software, you could.
If you wanted to load a driver or a kernel extension, you could.
If you wanted root or administrator access, it actually meant something.
Today, modern operating systems increasingly treat you less like an owner and more like a tenant in a corporate apartment.
You live there.
You pay for it.
But you do not make the rules.
Apple: The Blueprint for a Beautiful Prison
Apple did not invent the closed ecosystem.
They just made it beautiful.
They wrapped it in aluminum, gave it excellent typography, added good animations, and sold control as elegance.
And I get it. Apple machines are nice. macOS can be pleasant. The hardware is efficient. Apple Silicon is genuinely impressive from a technical point of view.
But the trade-off is real.
Modern Apple platforms are built around control:
- System Integrity Protection
- TCC permissions
- Gatekeeper
- App notarization
- Entitlements
- Secure boot
- Signed system volumes
- App Store rules
- Developer certificate revocation
On paper, this is about security.
In practice, it is also about authority.
Apple decides what is allowed, what is trusted, what is dangerous, what is acceptable, and what kind of software experience users are supposed to have.
And the deeper you go into the ecosystem, the clearer the message becomes:
You do not need full control. Apple will control it for you.
That sounds comfortable until you are the kind of person who wants to do something Apple did not plan for.
Run an older macOS version on a newer Mac? Good luck.
Modify system behavior deeply? Not really.
Repair certain parts without pairing, calibration, or official tools? Depends on the device and the year.
Install software that touches low-level parts of the system? Prepare for warnings, permissions, blocks, and workarounds.
And yes, security matters. Malware is real. Users need protection. Nobody wants a system where every random app can access your microphone, camera, files, keychain, browser data, and messages.
But we should be honest about the cost.
Apple’s platform is not only secure because it is well designed.
It is secure because it is controlled.
And control is profitable.
That is the part people often do not want to say out loud.
Android: The Open Platform That Slowly Forgot It Was Open
Android used to feel like the rebel platform.
It was the place where you could customize almost anything. Launchers, ROMs, APKs, root access, bootloaders, system tweaks, automation tools — Android felt like the opposite of iOS.
It was messy, but it was alive.
For power users, it was exciting.
You could install custom ROMs. You could root the phone. You could remove bloatware. You could change the look and behavior of the system. You could use the device in ways the manufacturer did not necessarily expect.
That Android still exists in theory.
But in practice, it is much weaker than before.
The modern Android world is full of invisible walls:
- SafetyNet turned into Play Integrity
- Banking apps refusing to run on modified devices
- Payment apps breaking on rooted phones
- Games blocking users because of device integrity checks
- Google Play Services absorbing more system functionality
- Manufacturers making bootloader unlocking harder
- Phones shipping with ads, telemetry, and preinstalled junk
- Apps depending on proprietary Google APIs even when Android itself is open source
This is the strange reality of Android now.
The source code may be open.
But the usable ecosystem is not.
You can still modify your phone, but the punishment is immediate. Your banking app may stop working. Your wallet may stop working. Some games may block you. Some apps may decide that your own device is no longer trustworthy because you dared to change it.
And yes, there are security reasons for some of this.
Root access can be abused. Malware can target banking apps. Device attestation can reduce fraud.
But again, the question is not whether security matters.
The question is who gets to decide what you are allowed to do with the device you bought.
If I own the phone, why is advanced control treated like suspicious behavior by default?
Why is a power user treated almost like an attacker?
That is the shift.
Microsoft: The PC Is Not Immune
For a long time, Windows was the last big mainstream platform where the user still had a lot of practical control.
Not open-source, obviously. Not clean. Not elegant. Not privacy-friendly.
But flexible.
You could install almost anything. You could run weird old software. You could modify the system. You could use local accounts. You could build a PC from parts. You could install Windows, Linux, BSD, or whatever else you wanted.
The PC was chaotic, but it was free in a practical sense.
Now even that world is changing.
Windows 11 already pushed the direction clearly:
- Strong Microsoft account pressure during setup
- TPM requirements
- Secure Boot expectations
- More cloud-connected features
- More ads and recommendations inside the OS
- More telemetry
- More integration with Microsoft services
- More friction around unsupported hardware
- More “recommended” defaults that mostly benefit Microsoft
And the trend is obvious.
The PC is being slowly reshaped from a general-purpose machine into a managed consumer endpoint.
That sounds dramatic, but look at the direction.
Your operating system wants an account.
Your files are pushed toward cloud sync.
Your settings are connected to online services.
Your browser is pushed toward a vendor-controlled ecosystem.
Your search bar wants to be an ad surface.
Your desktop OS increasingly behaves like a service platform.
The old idea of a PC as a neutral machine is fading.
It is not gone yet. You can still build a powerful Windows PC and do real work on it. Developers, gamers, engineers, and creators still rely on that flexibility every day.
But the direction is not good.
And pretending not to see it does not make it better.
Developers Are Losing Control Too
This should worry anyone who builds software.
A modern app is no longer just code.
It has to pass through layers of permission and approval:
- Code signing
- Notarization
- Store review
- Sandbox rules
- Entitlements
- Payment policies
- Platform guidelines
- Certificate systems
- API restrictions
- Remote revocation
Again, some of this is reasonable.
Users should not have to run random binaries with full system access. App stores can reduce malware. Sandboxing can prevent damage. Review processes can catch abuse.
But the power balance has shifted too far.
A private company can now effectively decide whether your software is allowed to exist on a platform.
Not because it is malware.
Not because it is dangerous.
But because it violates a guideline, competes with a first-party product, uses the wrong payment system, does something politically inconvenient, or simply does not fit the business model of the platform owner.
That should feel insane.
Imagine telling a developer in 2005:
In the future, you may not be able to distribute software to users unless a corporation approves your business model first.
They would think you were describing some dystopian sci-fi system.
Today, this is normal.
We adapted so quickly that we stopped noticing how strange it is.
Security Became the Perfect Excuse
The problem with this whole discussion is that the other side has a strong argument.
Security really does matter.
Most users do not want to manage system integrity. They do not want to understand bootloaders, certificates, permissions, drivers, app sandboxing, or package managers. They want the device to work. They want banking apps to be safe. They want their photos protected. They want malware blocked.
That is fair.
The old world was not magically better. It had viruses, broken drivers, browser toolbars, random cracked software, terrible update practices, and users clicking everything.
So I am not arguing for chaos.
I am arguing against pretending that every restriction is automatically good.
There is a difference between protecting users and removing ownership.
There is a difference between optional safety and mandatory control.
There is a difference between warning me and blocking me.
There is a difference between “this may be dangerous” and “you are not allowed.”
Modern platforms blur these lines on purpose.
And most people accept it because the locked-down version is convenient.
Linux Is Still the Escape Hatch
Today, if you want a computer that feels truly yours, Linux is still the closest mainstream answer.
Not perfect.
Not always comfortable.
Not always friendly to commercial software, games, hardware support, video editing, audio production, or professional creative workflows.
But honest.
Linux still gives you the feeling that the machine is actually responding to you, not to a corporate policy document.
You can install what you want.
You can break things.
You can fix things.
You can choose your desktop environment.
You can decide how much telemetry you accept.
You can use old hardware longer.
You can build a system that fits your workflow instead of adapting your workflow to the system.
That is why Linux matters even if it is not perfect.
It keeps the idea of a general-purpose computer alive.
And honestly, the fact that Linux is now the “advanced freedom option” tells you how much the mainstream platforms have changed.
Conclusion
We have normalized a strange relationship with technology.
We buy devices, but we accept that someone else controls them.
We call restrictions “security.”
We call surveillance “personalization.”
We call lock-in “ecosystem.”
We call limited repair “design.”
We call corporate approval “trust.”
And little by little, the general-purpose computer is being replaced by managed appliances.
The goal of this article is not nostalgia. I like modern hardware. I like fast machines. I like good battery life. I like secure systems. I like when things work.
But I do not like the direction.
Because power users are becoming anomalies.
Developers are becoming guests on platforms they helped make valuable.
And regular users are being trained to believe that ownership means nothing more than a monthly payment, a login screen, and permission to use what a corporation allows.
That should worry us.
Digital freedom was not destroyed in one dramatic moment.
It was redesigned into something more convenient, more polished, more secure, and much easier to control.
And most people will not resist it.
They will ask for more.
That is the part that scares me most.