/System/Library/CoreServices contains many icons in macOS Tahoe's new non-conforming icon jail.

But I'm most amused by icons like Wallpaper.app which can't be violating the rule by more than a couple pixels. Straight to jail!

The highlighted line, from the Swift stdlib, causes a jump onto the `emit.isolation` actor, if we're not already on that actor, even though the `trackEmission` function is otherwise nonisolated.

Can anyone explain what about the code causes that jump? Is this special handling of `isolation` as a first parameter? Or is there some other rule that forces the jump?

My only real association with the word "Tahoe" is Krusty's "Folsom Prison Blues" parody song from The Simpsons that begins "I slugged some jerk in Tahoe..."

It's quite catchy and nearly ends in a prison riot. I expect no less from macOS 26.

FB16424941 still isn't fixed in macOS 26 😞

It's a bug where, in SwiftUI MacCatalyst apps, if you put a button (or tap gesture) over a scroll view (including the safe area insetting the scroll view), parts of the tappable region won't respond to taps. It's weirdly changeable and unreliable, with different computers and seemingly even different monitors, having different effects.

As you might imagine, this can wreak havoc with floating toolbars, selection controls and plenty of other elements.

It looks like Swift 6.2 will *finally* let us access the built-in Swift demangling so we can turn runtime mangled names into something human readable without resorting to half-assed third party libraries (like my own CwlDemangle).

Technically, the demangling is part of the new `Backtrace` API but it offers `SymbolicatedBacktrace.Symbol` with a lazily evaluated `name` that performs demangling on the `rawName`.

It doesn't expose `DemangleOptions` but it's a huge improvement.

Does anyone know how to delete and recreate the passkey associated with their Apple Account?

Mine has stopped working (across all devices and all Apple sites). But the passkey doesn't appear in the Passwords app so it's not a simple thing to delete.

(I'm able to sign in with email+password but I'd rather get my passkey working, again.)

Frustrated by other code that isn't working, I decided to clown around with Cursor. It's like asking another dev to do the typing while you're pairing: you still need to know the steps and take over when it fixes a capture-self-before-init the stupid way (because of course it did).

However, I was delighted by this: accurate documentation lookup followed by correctly guessing what I was hinting at and immediately jumping into the refactor.

Xcode completion has a long way to go.

Why does iOS (a platform where bringing up a context menu requires a clunky press-and-hold that no-one discovers) have context menus that look so much better than macOS (where context menus are accessed via right-mouse and are a fundamental part of the experience)?

macOS definitely needs some love, here. In the meantime, I have to keep using popovers for everything.