Comment by jasoneckert
18 days ago
Imagine if Fedora locked you out of vi because your Red Hat account had an issue.
The unsettling part of stories like this isn’t “Microsoft bad,” it’s the growing assumption that local tools should be downstream of remote identity systems. A text editor is about as offline and fundamental as software gets, yet it’s now possible for account state, sync bugs, or policy enforcement to make it inaccessible on your own machine.
This is where non-macOS UNIX and Linux systems draw the line - if it’s installed locally and you have permission, it runs. Cloud services can enhance that experience (backups, sync, collaboration) but they don’t get veto power over whether vi opens.
When that boundary erodes, we start to see our systems as thin clients, instead of full local OSes, as the author mentions.
Business users want everything online, so anything can be accessed from anywhere. They want central identity, so when someone is hired or fired they only need to look in one place.
> if it’s installed locally and you have permission, it runs
On macOS, only after you've run xattr -c to remove the Gatekeeper block on non-Apple approved apps.
Didn't macOS apps get locked/took a ridiculous amount of time to open because Gatekeeper servers went down a few years ago?
https://www.engadget.com/macos-slow-apps-launching-221445977...
Not as bad as the bug described in OP, but still pretty bad.
Yes, there is still the occasional delay in launching apps due to Intertube check.