Bug fixes and performance improvements.
Posts
RE: @rhysmorgan@mastodon.social
Following up on this thread, yesterday GitHub began their rug pull in earnest.
Copilot is moving to a usage-based model, but instead of pay as you go, you get a set amount of tokens per month that *expire* at the end of every month. They've also completely removed free model access.
Are GitHub really aiming for four 8s of availability? Feels like it right now...
Holy shit, Control just got released on iPhone and iPad, cross purchase on the Mac App Store. It's also only £5 at the moment. A ridiculously good deal!
https://apps.apple.com/gb/app/control-ultimate-edition/id6502953520
I am not an AI doomer.
I enjoy using Claude Code. I do see it as a force multiplier for me, even if it's "just" being able to find the edge cases, parse large logs to narrow in on a root cause, or just damn well type faster for me.
But I've always felt the rug pull was inevitable. Compute costs + capex are unsustainable. I've always focused on getting useful, long-lasting artefacts (e.g. plans, scripts, tools, macros).
TERNUS!!!!!!!!!!! Yes!!!!!!
Like Apple got rid of the full-screen-covering volume toggle, can it please get rid of the full-screen MagSafe/charging indicator when you dock your phone? Please? 🥺
I had a sneaking suspicion that the single, collapsed async trick might be an (isolated Self) parameter in this week's @pointfreeco@hachyderm.io episode, having used it in my Unimplemented mock-generating macro. Felt good seeing it confirmed!
It’s an unbelievably useful trick – and it gives you synchronous access to the actor's state for the duration of the closure (with just the `await` to run the method)
Sadly, I don’t see an overwhelming appetite for learning, as many people are happy to ship code if the pipeline is green.
This has always been a problem, but definitely even more of a problem nowadays 🙁 Why bother learning when you can just chuck Claude at it? Let's ignore the fact that if you don't learn, regardless of everything else, you automate yourself out of a job…
Sharing this repo to demonstrate something I consider to be truly incredible in modern Swift with Approachable Concurrency.
Your View Models no longer *need* to be MainActor-isolated just because your SwiftUI View* reads or mutates a property on it. Your View Model tests can be totally nonisolated, and not have to mark them @.MainActor + experience MainActor-contention.
Thank you @mattiem@mastodon.social for showing me this is possible!
https://github.com/rhysm94/NonIsolatedViewModels
*and presumably UIView/UIViewController
So, so excited to be digging into these betas tomorrow!
@pointfreeco@hachyderm.io is one of the best investments you can make in your ongoing career as an iOS engineer, and I’m so excited to see both TCA 2, and to dig into DebugSnapshots for exhaustive testing for reference types!