Posted by ranebo 15 hours ago
Answer: Because modern-day Apple has subscribed to a particular brand of mitigation for the "noobs will always click 'Allow' especially if you ask them to first" problem. The mitigation is that Apple just dumps you on step 2 of a little 4-5 step mini sysadmin adventure where you prove, every time, that you're sophisticated enough to deserve an exception to the padded-cell walled garden mode they've sealed off 'for your safety.'
As a complete nerd, you'd think maybe I'd like that I can prove my skills like this, but it comes off as deeply disrespectful to me as the user that I can't disable this.
What's my solution to prevent grandma or a 10-year-old from clicking "Allow full filesystem access and keylogging" to an executable she downloaded from facebook-security-center-and-password-verification-cgi-bin-ab383 dot xyz? IDK, that's their problem, but they should offer a way for those of us who aren't clueless to turn whatever it is off.
You seem to have understood the problem. But then you didn't follow. If there was a way to disable this, first thing that the grandma would do is watch a video how to disable that and lose security from then on.
Of course it is not perfect, but their approach here is really decent. And also, if you find yourself needing to go through that often I think that's not a good sign security-wise.
It's gone so far that even tech people now think that having root access to a mobile device is somehow scary. Well guess what that root access is still there for the manufacturer. It needs it for stuff like updates. It just shields you from having any kind of input or visibility on what is going on.
And once you've given up your admin control to the mega corporation, your government is going to be next. They'll be demanding backdoors and regulatory bullshit like age verification and snooping backdoors. Even today the EU launched yet another chatcontrol proposal. Eventually they'll manage to get it through when they've paid off enough representatives.
Keeping full control is the only way to prevent this.
And even NSA backdoors could be discovered more easily if we had full access to our phones, obviously.
Not because she wants to install brew or something.
My grandma absolutely would not watch and follow a video on how to e.g. disable Gatekeeper, nor do I think she’d be able to if she tried.
Your grandma sounds substantially more tech savvy than my grandma. Good for her, she seems to know what she wants. Grown adults should be allowed to knowingly opt into an additional level of risk.
My litmus test for this sort of thing is Excel - I think we all can agree that Excel is used for way more than it should be, and the most complicated, unhinged uses of it are done by non-technical folks looking to get a task done through desperation.
With that in mind it ends up being weird to me in a way I can't articulate because after all I can speedrun losing a limb if you left me loose in Harbor Freight or speedrun losing all my money and becoming debt-ridden if you give me a laptop with internet connection.
Anyway, I know there's more nuanced discussion to be had still I sometimes wonder how would the ideal approach actually look like without requiring people to have a digital(ing) license before being allowed to connect to the internet.
To attack your specific example, cars have added all kinds of things that "hand hold" the user and keep them (and others) safe: Seat belts, air bags, anti-lock brakes, traction control, automatic emergency braking, back up cameras, lane keep assist, blind spot monitors, etc, etc, etc. (Oh, and guess what, per-mile traffic deaths are WAY down from a few decades ago).
Well, firstly, newer cars are now equipped with tons of safety features like various kinds of auto-braking, various warning systems which monitor blind spots in the car, and driving aids like lane assist, lane monitoring, what have you. And then they also have advanced telemetry features that don’t keep them safe, but their insurance company hopes will identify them as bad drivers if and when they get into accidents so they can be denied coverage. These could be analogous depending how you look at it.
Additionally while there’s not much out there for tools, I think that’s less to do with it not being an issue and more to do with it being kind of impossible? That said a few tools have things like sensors that detect the presence of fingers near saw blades and will not only stop operating, they’ll usually destroy the tool in the process to ensure the operators safety, because fundamentally, more saws exist, more fingers do not.
Like despite loving track driving, I wouldn’t think that everyone tearing around in V8 monsters with stripped interiors and roll cages is a good idea.
Generally I have to admit that society is trending towards making things safe(er) by default but as always with every trend some attempts at following or complying are executed poorly (intentionally or unintentionally). Here's where I agree that while some safeties are universally good and people that disable them suffer from overconfidence I have seen some examples like experienced people removing the shields from brush cutters because they can get in the way and increase the risk of a tangle when cutting overgrowth (though you have to be mindful and careful to not fling small rocks around afterwards).
And yeah, I see your last point and generally agree but for fairness sake I would like to present the other extreme end where a person on a bicycle against a pedestrian is also dangerous albeit less so. That said I'm about to accidentally argue in favor of the "guns don't kill people..." rhetoric and I really don't want that so I will concede that for the time being it's better to (thoughtfully) design safe systems instead of relying solely on operator diligence.
Oh how I dislike that objectively I recognize the need for safety yet subjectively I disdain the fact that my tools try to nanny me and I can't reconcile these two views :/
A discussion on which I think we'd absolutely agree. But yeah, it's a thing, whether we agree with it or not.
> Generally I have to admit that society is trending towards making things safe(er) by default but as always with every trend some attempts at following or complying are executed poorly (intentionally or unintentionally). Here's where I agree that while some safeties are universally good and people that disable them suffer from overconfidence I have seen some examples like experienced people removing the shields from brush cutters because they can get in the way and increase the risk of a tangle when cutting overgrowth (though you have to be mindful and careful to not fling small rocks around afterwards).
Oh 100%. I would argue most safety features, even when implemented well, will encumber those who were already skilled, which is why you rub against the ones in MacOS. It just... I don't think there's a way around that, you know? Think it's just an immovable law of the universe.
> Oh how I dislike that objectively I recognize the need for safety yet subjectively I disdain the fact that my tools try to nanny me and I can't reconcile these two views :/
I struggled with this for a long time too, but for me, it kinda resolves with the following reasoning:
On balance, safer... everything... makes for a better society, because it enables more average people to do more things, to go more places, to use more technology, to make their lives better. And the fact is, for more experienced people, we can get around this.
Like the security constraints in MacOS are a great example: they are fucking ANNOYING when you're configuring a new Mac, completely agreed, because every last thing requires so many steps. However how often do you really find yourself needing those options in daily driver use? I can count on a hand the number of times I needed system access the last couple of weeks (and usually it's just an app update where I have to give the app the go ahead by typing in my password). The last time I had to open security options and do that whole procedure... it would have to be weeks at minimum, perhaps even months.
Except when it becomes a reputational problem for the OEM: Excel sucks at X (i.e., don't use it for that) and Excel sucks can become equivalent in many people's minds.
Sometimes it is actually a problem of people 'holding it wrong' (as the meme/trope goes). And who gets the blame?
I guess sadly the press will gloss over all the intricacies for a few clicks.
I also feel that dumbing things down probably just exacerbates this problem as "reasonable folk" have no clue how you actually get from a to b.
On the flip side, many websites ask if I want to allow notifications. I almost never do. I was looking at settings recently and surprised how often I’d clicked yes by accident (maybe about 5% false click rate?)
One of the first things I disable on any new Firefox setup. I want zero notifications from websites (or in general, one of the objective improvements of Windows 10 over Windows 7 is that you can just disable notifications entirely, while disabling balloon alerts in Windows 7 was a huge battle that never fully worked)
But like most of the AWS Console, each service is different in a unique way.
My mother recently had "There are antivirus notifications taking over half the screen, do I need to click on them and renew Norton?"
She'd been somewhere and done something that had allowed an unscrupulous site to flood her with alerts directing her to give payment information to a scam site pretending to be antivirus renewal.
When I finally got over there (she doesn't live on the same continent) I went in and disabled notifications on all of her installed browsers.
As far as I'm concerned the whole 'let this website notify you' feature is an antipattern and yet another example of browser overreach.
It's a symptom of the whole "we converted our document platform into an application platform" debacle that typifies the modern web.
Notifications make no sense for the majority of websites, but if you use, say, a web-based email client, then you probably do want them.
Yes and no. Prompting for it modally the way they do now is for sure wild, but for some webapps (e.g. Slack) it makes plenty of sense. I think Firefox used to have a UI they used for some things where they'd inject a non-modal bar with a couple of buttons inside the content area. This sounds like the right type of UI, maybe at the bottom of the viewport.
site.com can send notifications when you're not on this site. (Get Notifications from site.com) (Dismiss)It’s used for writing keyloggers.
That’s it. It’s the permission that lets you write a keylogger. It SHOULD NOT be just a click away. It should require some extra song and dance, because this is an especially dangerous permission, and the extra friction is justified.
Apple should throw this whole thing out and replace it with first-launch lists of permissions, with toggles for each. This app 'Zoom' wants "Record the screen, microphone, camera." Then you're done and you don't have to keep searching for it in little lists and relaunching it.
There have been alarm bells ringing in my head for a long time with all these settings, and the fact that they’re buried in the settings app gives me a lot of peace of mind. I’ll click through a lot of boxes and alerts and grant permissions that I shouldn’t. I’m SUPER glad that I won’t accidentally grant, you know, full disk access or accessibility to an app just by clicking on a box that appears at startup.
I remember back in the bad old days when I was constantly making extra user accounts just to run some program. Kinda sucked. Hard truth is, you sometimes want to run code that you don’t fully trust.
Well, if you feel that way, they do make platforms that sound like a better fit: iPad, iOS, even Android kinda fits that mold. I would call them "toy computers" but that is my bias. It's not a real computer to me if I am not even in control of what code runs on it.
Linux is also doable, but there’s extra work involved with setting up separate user accounts for running specific pieces of software, configuring namespaces for those processes, that sort of thing. But this is backwards. I’d rather start with a secure default state and have to configure exceptions. Back in the day I could get that from SELinux strict policies but it seems like those have fallen by the wayside.
For previews, Apple could provide an API for this very common task. The OS can provide the images, and they could be sampled at refresh rate that makes it unusable for arbitrary recording.
For key chords, they could repurpose the emoji key, which is currently not available for external binding, to effectively allow capture only following that magic sequence. The OS should manage this centrally, allowing a program to define its commands and then delivering only the command without the specific associated keys presses. We get the benefit of centralized management with deconfliction, too, which is a real pain on macos as it stands.
I don't know if these solve every problem, but they solve some. There are probably better ways. Apple has plenty of smart programmers. The product team needs to let them solve the problems that they surely know bother their professional users.
As nerds, do we have a higher capacity to fix a mess than a grandma? Sure, probably, but that doesn't mean that we don't make messes.
Tried some little throwaway app and realized you don't need it? Sucks for you. It added itself to your login items and it'll start up in the background every single time you turn on your computer. And it won't even tell you. Thought you deleted the app from your Applications folder? If you didn't check your login items, there's probably some little script that deeply installed itself and it'll reinstall it in the background during your next startup.
Adobe is the fucking worst with this. Their Creative Cloud spyware keeps enabling itself and reinstalling itself so long as you use photoshop. And it'll constantly find ways to turn itself back on. Steam also adds itself to login items, which is fucking annoying because you'll reboot and be hit in the face with game ads. At least it respects your decision when you turn it off, but login items should be opt in, never opt out.
$ brew uninstall --zap aerospace
Usually it blows away everything associated with the app, including cached files, configuration in ~/Library and ~/.config, etc. Very useful. It'll leave a non-functional login item which isn't active and can't be active.For .pkg files, there's UninstallPKG which reads the package manifest and properly uninstalls it.
Speaking of packages, even more embarrassing, Microsoft Windows literally beat them to shipping a first-party package manager. I feel like Apple lives in a fantasy land that the drag’n’drop app install method from the classic macOS is some kind of platonic ideal — never mind that they can’t stop half the apps out there from going outside that paradigm and installing their crap all over the place.
There might be some way to design a system from the ground up to avoid this problem (some kind of declarative, capability-based security?), but retrofitting that onto an existing behemoth of a system does not really work.
GP was saying that systems should be "transparent enough that a compromised system is obvious". I'm not entirely convinced that that's possible (On Trusting Trust should have taught us that compromised systems can create places for the compromise to hide), which means that the salt flats analogy is not a great analogy, IMHO. But at least now you understand the analogy.
As a self proclaimed complete nerd I expect you to be insufferable about this—lo and behold...
Let’s not pretend these security practices have no use, please. This “I’m such a greybeard, screw modernity” playacting is so tiresome it’s not even quaint any longer.
But it is funny to see the daily barrage of permission prompts fly through when macOS made an entire ad ridiculing Vista for half the popups and permissions macOS requires these days.
Even though a bunch of the responses are "well you don't want a keylogger" when the first solutions I can think of are also (potential) keyloggers. :)
I'm not sure if it's what you're asking for, but you can disable SIP:
https://developer.apple.com/documentation/security/disabling...
At some point Apple realized the "power user" market was too small, and they were better off treating all of their users like idiots. And that's when I left.
Desktop power users were on the Acorn, Amiga, Atari and PC.
As NeXT "acquired" Apple, Linux users thought OS X was the UNIX experience they were looking for, and since they were never part of Apple culture, keep getting their expectations wrong.
They never set out to build the ultimate power user machine, their target was still general consumers. They just happened to have the right product at the right time when everything else just failed to compete.
Had desktop linux been in a better state, or had MS built WSL earlier, things might look a lot different today.
Here's a Titanium PowerBook G4 ad that says "Sends other Unix boxes to /dev/null": https://www.reddit.com/r/vintageunix/comments/b4kojo/sends_o...
Here's a snapshot of the software solutions page for the aluminum PowerBook G4 from November 2004, proudly touting Unix and even X11:
https://web.archive.org/web/20041126011836/http://www.apple....
Some quotes from the Power Mac G5 page (https://web.archive.org/web/20041126015955/http://www.apple....) from the same era:
"With the Power Mac G5, a researcher can now run both productivity applications and high-performance UNIX applications on a single system. Mac OS X Panther includes 64-bit optimized system math, vector and image libraries that take maximum advantage of the 64-bit G5 processor."
There was also a cluster in Virginia made of Power Mac G5s, which Apple also touted.
I also attended a marketing session at CERN, when they came to visit our IT department in 2003, when there were still people using Sun pizza boxes as their desktops (aka SPARCstation).
Anyone that has been around Apple long enough can recognise the old Apple (pre-OS X), on current Apple, now that they can be their old self.
Any good biography on Steve Jobs, like The Next Big Thing, Folkore or Cult of Mac, will show that underlying culture.
Microsoft had "WSL" earlier, only badly.
The only reason I started with Linux at home back in 1995, was the half hearted UNIX subsystem on Windows NT.
Had they been serious about it I am sure GNU/Linux would never taken off.
As shown by Apple sales of folks buying POSIX instead.
That market always bought the cheapest machine (or "best value", by specs/$) they could find (or, if they were really an "idiot", the machine that Best Buy had the highest commission on), which would be a PC.
In the beige days, Apple's bread was buttered in the publishing market, once they moved to OS X, they got the "professional nerds who wanted UNIX but not doing sysadmin at home".
I'd call the power user market that - the kind of idiocy that's more interested in the process than the results.
The actual target market was "people that have a life outside computers".
csrutil disable
nvram boot-args="amfi_get_out_of_my_way=0x1"
I really wouldn't recommend doing either, but you do you.
But do that and the very next thing that happens when you try to open a browser or a link in an email?
"Your browser has been changed from Safari to Chrome. Would you like to use Safari or keep using Chrome?" and for a little salt, the default is "Use Safari".
Some third-party software pretends to restore this functionality, but they do it by repositioning the mouse to simulate a hover, which introduces a delay and doesn't integrate correctly with the animation. Someone wrote a patch that works by disabling SIP and injecting code (https://github.com/briankendall/forceFullDesktopBar), but eventually stopped maintaining it.
A decade later, I doubt anyone at Apple remembers that this bit of user interface used to be good.
I never noticed that behaviour because I only use mission control in full-screen mode. If you swipe up with three (or four) fingers from a full-screen window the previews are visible immediately. I have no idea why we need a different preview for desktop vs full screen however.
The part of this UX that annoys me is the spaces get re-ordered for no apparent reason. I usually have a few IDE windows open and it's tiring to have to double-check the window hasn't moved.
The non-fullscreen (desktop) case uses an animation for the same purpose, locating the current app window in a sea of others.
So what would the preview be in the swipe-from-desktop case? A preview of the window-sea, or the desktop as is? What should the animation be? I suspect those questions are why they chose to just name the desktop.
I think it would be more consistent if the tab based preview only existed for the desktop window-sea and transitioned to the actual space previews when swiping between spaces.
Previews are also visible immediately if you set Mission Control as a hot-corner action. In never see the title-only spaces — i forgot it even did that until this discussion.
I also wish I could name the Spaces. "Desktop N" is pretty useless.
However, swiping beetween the previews, it sometimes jumps to random places in the order - which is not nice.
Possibly a bug, but I might as well just write this as a letter to Santa because it's got more chance of being read than a feeback.
The setting is "Automatically rearrange Spaces based on most recent use" which explains why the behaviour felt so intermittent.
Wouldn't it be great to have them named "Design", "Dev", "Productivity", "Games". Or whatever makes sense given your needs, instead of simply desktop #.
Multitasking and context switching has been increasing for years, instant messaging boosted them again, and agent-based workflows are only going to push further in that direction. The OS needs to support that, and it's not an app-level concern: I use the same apps in each of my tasks.
IDEs can help with this of course: they tend to have workspace/project primitives and can restore code and terminal contexts from those. But there's always a bunch of other connected stuff that can't be linked: web pages (some IDEs are starting to manage those too), agents which don't reside in the IDE, relevant chats with colleagues, project management apps and so on.
This is clearly an OS-level concern, not an app-level concern.
Some of the iPad experiments with alternative window organisation looked kind of promising, but they’re just not powerful or intuitive enough IMO.
¹https://blogs.kde.org/2026/01/17/streamline-plasma-with-acti...
Sadly wm in MacOS is like notifications on iOS: with enough time you get used to the unproductive mess they are, but you'll be missing out on better solutions. And since probably all MacOS devs are using Mac, they won't see/understand other (better) approaches.
With the app "AltTab" I can at least switch between my apps without using the mouse and with raycast I can position windows, but it is painful how much slower switching and positioning things in MacOS is, than in any tiling window manager.
However, why startups outperform big companies isn't just the skill gap. Even if you have the most amazing leadership in big tech it is monumentally difficult to move the needle on some problems purely because of size not because of incompetence. All I am saying is don't overindex on perceived intelligence. A big org can start looking pretty dumb even though it is still far right of the bell curve compared to even a startup (hypothetically). Org size and the constraints that brings are a significant factor.
While linear window management is clearly not to everyone's taste, I still think it's a valid idea! It was heartening to see this launch and its reception, as I'm actually working on something in the same area right now...
I spent an hour today trying to get it working the way I’d expect and it still does odd things, like after disabling automatic reordering based on usage the order is different when 3 finger swiping previews as opposed to actual windows. The visual order is as expected but the swipe order is not linear.
I hate that design and what it has done to Gnome.
A grid was so much better.
Also, everything has excessive padding now. Modern Windows control panel UIs often feel like a multicolumn wall of text with lots of empty space and a few switches dropped in, and to fit the same amount if options as the older UI they had to either hide some toggles because "known needs them anymore" or introduce extra intermediary navigation steps. As a result the new Control Panel feels bloated and less useful.
Two decades ago was 2006. I have the same desktop experience today as I had two decades ago (Fvwm2) and have had the grid virtual desktop layout this author misses so much for the entire time via the Fvwm2 (and Fvwm before that) virtual desktops feature. One of the reasons I switched to Fvwm (I no longer remember when, but sometime in the mid to late 1990's) was the grid virtual desktops feature. So I've had gridded virtual desktops for longer than twenty years. Fvwm2's configuration has been tweaked and adjusted slightly along the way, but at no time did a corporate designer decide that I no longer should have a feature I had previously been using.
Proprietary software does not have your interests at heart, it has its stock price or next quarters sales numbers at heart, nothing more.
You never ever had a single software change its workflow?
Radical workflow changes with no recourse is the standard in proprietary software, not so much in FOSS.
Jokes aside: yes, I can see how it's technically possible to never experience a workflow change. But also using the same tools at work, your kids school, family you help etc. I just find not very probable.
The great Gnome 3 rollout did this for me... to be fair I guess that was a decision of the distributions, but it was in concert with the developers who decided to make a hard changeover, EOL the gnome 2 line there and then, and (deliberately?) scupper the possibility of installing both 2 and 3 on the same system.
Either way it sucked and that pushed me to Xfce, which I still use on linux. But it goes to show it can happen in FOSS.