Jared Sinclair

@jaredsinclair
682 Followers
235 Following
754 Posts

developer n’ designer • I make @moxtopper • also ’Sodes also many (cr)apps that never shipped • Oldsmobile man. • former nurse • bad writer • Cleve Land

“Silence, exile, and cunning.”

Homehttps://jaredsinclair.com
GitHubhttps://github.com/jaredsinclair
Twitteraych tee tee pee ess colon slash slash fuck dot off dot com slash &then=die
MTG Life Trackerhttps://moxtopper.com
The Home Screen seems decent still too. If it ain’t fix it, don’t broke.

I don’t think I’m going to change anything in ’Sodes for iOS 26. It’s already harmonious with the new navigation design but I like mine better.

Maybe if I had to support iPad I’d think otherwise.

Icon Composer is pretty fun. I wish my app needed more layers.
My favorite change in iOS 26.
@mattiem This same code used to crash circa November 2024. Running it today, with Xcode 16.3, it no longer crashes. Exactly when (and how) did Swift stop over-eagerly inserting main actor isolation checks in code set up this way?
Look at this shit. Bastards. Their jackassery knows no bounds.

Small potatoes in this world, but I’m still pissed: my app @moxtopper has been wholly ripped-off by some assholes from the Netherlands: their app Lotus, by “Vanilla b.v.”

Look at these screenshots; they’ve copied everything down to the fonts and layouts and iconography.

Swift Concurrency Pop Quiz!

Given the following base method (ignore the periods below; @-symbols are annoying):


func someMethod(
block: @.isolated(any) () async throws -> Void
)


How does the presence of various combinations of these additional keywords on `block` affect whether the value of `block.isolation` is the caller’s isolation or `nil`?

sending
@.escaping
@.Sendable
@._inheritsActorContext

NO CHEATING. Guesses in the thread 🧵

cc @mattiem