With reduced-motion enabled (which is basically required in Tahoe :eyeroll:), animations complete immediately and there is no chance to click the salt/water.
Is this where I can complain about command+q? All day every day I use command+tab/tilde/w/a/s, and smack in the middle of that is command q. It's like if automobile manufacturers decided to put a third pedal between the accelerator and the brake that immediately shuts off your car in the middle of the highway. And you can't disable it, instead you can map it to such helpful things like... invert colors.
For me it’s Ctrl + C / V. I will frequently hit Ctrl + C when I want to paste, and some software helpfully copies a blank line to the clipboard if nothing is selected, thus erasing whatever I copied.
Get a clipboard manager. Being able to access my last 20 copies instead of only 1 is definitely something I wish I set up a decade before I did.
Not only useful for mistakes but also just if you jeed to eg copy someone's bank info to separate fields without doing 4 switches from invoice to bank app
Not only can disable it, but with the right tools like Karabiner elements you can turn it into something useful - double tap cmd+Q to quit: no accidental activations, but retains muscle memory
With Linux systems, if there wasn't a configuration option to override something, you'd be able to create a fork and still do it. So low level layers in Linux have become flexible enough that you do not need to do it, even if there are opinionated UIs on top.
The same levers are on macos too. People are getting caught up someone wrote a tool and released it. The fact that someone wrote a tool and released it shows it's possible and these levers exist.
In System Settings > Keyboard Shortcuts > App Shortcuts, add the shortcut: app Safari, name "Quit Safari", command-option-Q. This will leave command-Q doing nothing, yet still allow you to quit. Repeat for other apps.
You can't do that because the design of the whole system is dumb - instead of matching by unique (within the app) universal (=across apps) menu item id like "quit" that's hardcoded into the framework, you must match by menu item displayed name "quit Safari", which is different for every "quit MyNewShinyApp"
PS: and sometimes the name string is also dynamic "Navigate to the latest folder named XYZ", so you can't match at all!
I'm of the opinion that over-hiring was a strategic move to make hiring more expensive for competitors. Look up those popular profit-per-employee lists that circulate now and then. Spending $1 to make hiring $1 more expensive for your competition makes business sense. And even if Bob and Sue and Jim and Alice have redundant roles in the company, that's three competitors who couldn't fill that role. Does Google _really_ need a South Lake Union office location? Probably not, the entire building is likely redundant. But it siphons talent from the neighbors.
I’m absolutely not AI, I dedicate this morning to technical discussion with HN community on my post, which I’ve spent weeks building the technology behind it
Does the browser expose its accessibility tree instead of the raw dom element tree? The accessibility tree should be enough, I mean, it's all that's needed for vision impaired customers, and technically the ai agent _is_ a vision impaired customer. For a fair usage, try the accessibility tree.
The accessibility tree is definitely useful, and we do look at it. The issue we ran into is that it’s optimized for assistive consumption, not for action verification or layout reasoning on dynamic SPAs.
In practice we’ve seen cases where AX is incomplete, lags hydration, or doesn’t reflect overlays / grouping accurately. It does not support ordinality queries well. That’s why we anchor on post-rendered DOM + geometry and then verify outcomes explicitly, rather than relying on any single representation.
reply