While my SwiftUI knowledge remains quite limited, the more I learn the more I suspect that “because it’s in SwiftUI” is not a sufficient explanation for why the new macOS System Settings app looks and behaves the way it does.

It’s still fun to go out with an iPad as my “ultra-lightweight” machine—in my case, a 2020 iPad Air and the Keyboard Folio. In some ways, it’s really hard to beat, although in other ways, it’s still irrationally frustrating. Definitely curious what iPadOS 17 will bring next week…

Me: I wonder if I should make my app subscription-based rather than a single purchase…

Also me: Maybe see if you can write the app before you worry about pricing models, hotshot

As much as I appreciate Hello Weather, I think I’m going back to Carrot. It has more detail, better widgets, and a much better iPad app.

I’ve never been a multiple-monitor person, but having Hacking with macOS open on the iPad Air in portrait mode next to the Studio Display is pretty great.

I’m trying to learn Swift as my first “non-web, non-scripting” language in literally decades. It’s exciting, although I’m clearly swimming against the tide in focusing primarily on the Mac. (If the project happens, I’d want it on the iPad, too, on general principle.)

Watching the first seasons of “Midsomer Murders” with my mom. This show was sure keen on working gay panic into the plot even when it had no connection to the case.

Following my earlier thought: going with SwiftUI would limit my audience (only Mac and possibly iPad), be far harder to do (I’ve really only made web apps, so I’d have to learn from scratch)—but it’s probably the right choice, because I think that’s the version of the app I’d most want to use.

Continuing to noodle around with a fiction brainstorming app idea, but also continuing to dither on whether to do it full server-side web in Elixir, more SPA-style (which offers a possibility of Electron-based desktop apps), or learning Swift & SwiftUI for desktop-only (and Mac-only).

You may think all HDMI cables are the same, but I tried an AudioQuest® HDMI cable recently as an experiment and discovered a profound difference—the number of HDCP errors my Apple TV reported went up by an order of magnitude!