Now have Categories that pops up when choose the new workout type. Whole extra choice screen.

I can make out the types of workouts when I choose them, without my glasses, partly because of icons. This one is unreadable

So many extra taps required to start a workout and if you do a multi-type workout (+ button).

I do use class a lot of the time, mostly because I have a rich document hierarchy (imagine PowerPoint built on top of SpriteKit).

I mention these issues because the ARC one in particular surprises many.

Also some stuff in SwiftUI works better with structs, eg FileDocument

Swift nuances:
Structs containing reference types is a red flag if they are passed a lot (ARC).

Structs as @State in SwiftUI act more like ref types and a @Binding to such is effectively a ref type.

Look for mutating func in structs as @State - semantics more like C++ const objects = changeable.

I’ve been calling Swift “Modern C++ without the C” for years.

Ported Touchgram from C++ using Cocos2D-x to Swift and SpriteKit back in 2018.

Have now written about 60 kLoC Swift after 25 years of C++, including some very grungy CAD code.

Will still do C++ for $$ but not gonna choose it first!

SpriteKit to video, with a Metal preview.

Also means I could run it on my 27” Intel iMac “design machine “.

I agree with the need for a Command abstraction. I have a backlog of a few articles to explain stuff, now I’ve shipped the Mac version of Purrticles.

I made Purrticles as a Multiplatform SwiftUI app partly to avoid any complications from Catalyst, especially as am doing things like rendering

I'm a bit tight for time & avoiding rabbit-holes, this stuff is teflon-lined for me.

github.com/AndyDentFree... is some of the public stuff I did in similar manner but focused on evolving polymorphic hierarchies, like game encoding.

Done lots of complex format & movie enc/decoding over the years

Quick thought without much diving into code or CBOR

If you're just creating a protocol for type checking, consider a way to register a closure to invoke on hitting instances.
Breakpoints can only take you so far for repeatable debugging.
Log points in code help regression testing.

and I'm here to say they've done a great job on a clear rewrite that supports creators
okaydev.co/terms-and-co...

Glad to see your response.

I call these things out because:
1. sometimes, it really is a biz (or junior lawyer) trying to get away with it
2. creatives, especially, should pay attention to what we sign &
3. "we don't mean it like that" terms count if someone gets acquired & suddenly are enforced.

"SwiftUI in 1D, 2D and 3D."

I'm still stewing about this.
1D = menubar app?

Would 0D be a voice-only interface where you use result builders, or is that cheating to call it "SwiftUI"?

I released my first Mac app (in decades) last week, built with SwiftUI. It's a common codebase with the iPadOS and iOS screens. Purrticles has one big document window with 3 panels showing Xcode-style controls.

There are 57 `#if os(` occurences across the 4387 lines of Swift code in my Views.

Has anyone explained how these tariffs work when a US studio films overseas?

Say 90% of the budget is a couple of US stars but all shot in Toronto?

What is being “tariffed”?

The Touchgram family is all about tactile app naming.

apps.apple.com/au/app/purrt...