So @oskargroth pointed Claude and Hopper at SwiftUI to try to figure out what's going wrong with List performance, and it has a scathing take on the architecture it's discerned from the disassembly…

"this is the code of a team that's been debugging reuse failures for years. They've been patching and optimizing within the architecture rather than questioning whether the architecture is right for this use case."

(/via the site we don't talk about)

Hopper's MCP in something like Codex is *killer*. I can ask it things like, 'what private API could I use to make a UIKit window dockable on visionOS', and it will just figure it out from the disassembly, same way I would — just a lot faster.

Its solution matches the one I reverse-engineered myself a while back (https://github.com/steventroughtonsmith/VisionImmersiveDockableUIKit/blob/main/VisionImmersiveDockableUIKit/Source/Application/VVUDockableWindowScene.swift)

Here's one for the icons-in-menus haters on macOS Tahoe:

defaults write -g NSMenuEnableActionImages -bool NO

It even preserves the couple of instances you do want icons, like for window zoom/resize

/cc @gruber

Google has news on what you will need to do for still being able to sideload apps:

* enable developer options
* confirm that you are not tricked
* restart phone and re-authenticate
* wait one day
* confirm with biometrics that you know what you are doing
* decide if you only want unrestricted installs for 1 week or forever
* confirm that you accept the risks
* enjoy the few apps that still have developers motivated to develop for a user-base willing to put up with this

https://goo.gle/advance-flow

This is a WILD take, but hear me out: Related UI elements should not appear unrelated

https://rakhim.exotext.com/related-ui-elements-should-not-appear-unrelated