If you’ve ever thought Apple isn’t opinionated on app architecture, look again. App Intents has a type called AppDependencyManager built-in, which promotes injection of dependencies, and they even recommend using it in the main app target, setting it up in your App’s init. Buttons and Toggle can take an AppIntent. It’s almost like Apple built their own optional alternative to PointFree’s TCA.

https://developer.apple.com/videos/play/wwdc2025/244/

https://developer.apple.com/videos/play/wwdc2025/275/

https://developer.apple.com/videos/play/wwdc2025/260/

https://developer.apple.com/videos/play/wwdc2025/281/

Stop personifying LLMs. It assigns agency and responsibility to a tool, and we all know you can't blame (or credit!) the tools.

My LLM wrote this code, and then committed it.
↓
I wrote this code and committed it using an LLM.

Getting this language wrong skews our relationship with our tools. It lets us dismiss our responsibility to check and correct the output, while preventing us from crediting ourselves for the final result.

What it means to be human should grow from new tech.

Running a desktop OS on a phone chip… It’s marketing and cost-savings.

Running a desktop OS on a phone… That’s a game-changer, and one that’s happening on the Android/Linux side.

I hope the Neo is a prelude, not the main act.

Hot take: People who think the MacBook Neo is a game-changer have never heard of the second-hand market.

(Or they appreciate pretty colours ✨)

@nileane I’ve recently concluded for all I don’t much like the LLM situation, or maybe specifically because I don’t like it, I need to educate myself on them early to face the future on my own terms.

I want to avoid the subscriptions for stolen data. Give a tool any responsibility, and you get the Post Office scandal.

But they’re getting more efficient. Give it a decade. Ethically trained models, running on-device, mostly delegating to scripts, user confirmation for destructive edits & IO?