Dustyn August

Still hopeful though. 🥲

Another year of me trying to think of another lottery where the content creators and internet personalities win every drawing. Definitely an interesting version of random.

At this point AI slop systems are the same as as Terrence Howard “proving” that 1x1=2. You cannot change my mind.

Believing Claude finds your questions insightful is like believing the stripper actually likes you

SF Swift and Apple platform developers! 🍎 Join the SF SLUG x CocoaHeads meetup at @lyft HQ on Thursday, March 12 at 6 PM. 🥽 Steven Pease on visionOS 🤖 Arnold Laishram (@arny_laishram): Deterministic UI testing with AI Agents Space is limited! Snacks and networking included. RSVP to save your spot: luma.com/q3qfl6pw.

@stephencelis I was afraid you’d say something like that. Though I am not at all surprised. 🥲Just one more item for the good tradeoffs of TCA. No matter, it should be fun to see how you guys accomplish this! Looking forward to the new series of PF videos.

@dustynaugust While technically possible, I don’t think it’s feasible with ad hoc models. You’d need to maintain an actor and class wrapper per model that duplicates the actor’s interface, and that’s just one part of it. TCA2 gets to achieve this easily because the Store is so generic.

MainActor models destroy potential test parallelization. It even came up recently on the forums: forums.swift.org/t/improving-sw… Luckily TCA2 doesn’t have this problem :)

It’s all fun and games until an entire economic class is priced out of access to tools. 🙃

Happy holidays everyone! We’re excited to announce our first-ever South Bay event, hosted by our friends at Netflix. Join us on January 8, 2026 to kick off the new year with the Bay Area Swift community. RSVP here: luma.com/gx81vj3l

I’m more and more convinced that the more bullish an engineer is on AI, the more likely they are to be either absolutely brilliant or complete dogshit.

“let’s get on a quick call” why. why must we get on a call to discuss something that can be resolved on text with 4 extra brain cells and 2 more sentences of effort. absolutely torturous habit of people requesting calls for everything. 😤🚩

Surely we’ll definitely keep the same humanitarian all life is precious energy going the next time we talk about immigrants, Palestinians, and **checks notes** literally school children, right? Right?

@seanallen_dev @_DavidSmith I had a similar discussion at work today. Since you have to manage two versions of code either way, the question is whether you prefer to keep that work in “one” place or spread across many small places.

For the Roast App iOS 26 update, I'm trying a technique I heard from @_DavidSmith where I duplicate all my views between iOS 18 and iOS 26. Sounds crazy, I know. For example, "iOS18RoastView" and "RoastView". The iOS 26 variants can fully adopt all the Liquid Glass goodness without availability checks everywhere in the view (I'm also redesigning each screen to my taste). Sounds crazy at first. But David explained it well. When the time comes to remove support for iOS 18 next year, I just have to delete all those iOS18 specific views and we're free and clear going forward with the new iOS 26 versions of the app. This has an added benefit for me because I acquired this app, and it's not my codebase. So by clearly separating the iOS 18 version (with duplicated files), I can make the iOS 26 version of the code MY code. It's a clear changing of the guard. I like it.

We’re now on Luma! Swift Language User Group SF × CocoaHeads now has a new home for RSVPs and updates. Check out our calendar for upcoming meetups: lu.ma/sfswift

We’re lining up speakers for SF CocoaHeads (Swift Language User Group)! New and repeat speakers welcome. Pitch your talk here: forms.gle/h1Xe4AoD9Jevw7…

> SwiftUI really doesn’t want you using MVVM. This doesn't seem accurate, and it's an incorrect deduction to make. TabView’s behavior in not persisting state for its children doesn’t have anything to do with choosing one architecture vs the other. As for your solution, I would suggest caching data and not views (which should avoid you having to heap allocate those AnyViews). We generally suggest thinking of the view as just a description of what to render and not having a persistent identity. Generally, it’s the data that drives the view, and the view itself is just a transformation on the data, ideally as a pure function.

🚀 Swift developers in the Bay Area! The SLUG x CocoaHeads meetup is back Thu Jul 17, 6‑8 PM @ Lyft HQ (185 Berry in SF). Hear Airbnb’s Kieraj Mumick (@kierajmumick) + more, grab snacks, and meet others in the community before post‑event drinks. Space is limited—request your RSVP now! 👉 lu.ma/6pu9dl52

@azamsharp I’ll double check with my co-organizers too and circle back should I hear anything different. Either way enjoy the trip!

@dustynaugust Thanks! Appreciated. I arrive July 16 around 12 noon CA Time. July 17 looks like it is going to be really busy. July 18 might be available but not sure if the dates will match with SF user group schedule.

I will be in San Francisco July 16, 17 and 18 and would love to speak at a local iOS meetup about Foundation Models Framework. Is there a Twitter account for SF iOS Meetup?