Will

let's express gratitude to the amazing people who selflessly shared their priceless wisdom with us: @danielchooper.bsky.social, Jinkai, @useyourloaf.com, Tjeerd in 't Veen, @jacobstechtavern.com, Bruno Valente Pimentel, Alfonso Tarallo, @massicotte.org and @will-lumley.bsky.social

Hard agree. Combine deserved a graceful evolution, not quiet abandonment. Even a small set of first-party bridging tools or async-friendly operators would’ve gone a long way toward easing the transition.

My talk from ServerSide is up!

Fair question! And a common gotcha I've had with AsyncStream.

In this case it’s fine, as each call to stream() creates its own independent AsyncStream/Continuation pair, and the actor fans out values to all registered continuations when send(_:) is called.
So yeah it’s multi-subscriber safe :)

Why make this?
Because observing an @Observable class from a SwiftUI view is easy, but doing the same from another ViewModel got messy fast. Without @Published, you’re left juggling Tasks and AsyncStreams just to stay in sync.

🚀 New blog post!

AsyncCombine: Because Async Code Shouldn’t Be Ugly

I brought back Combine’s sink, assign, and CombineLatest - but built powered by Swift Concurrency.

Observing @Observable from another ViewModel shouldn’t be painful.

Here’s how I fixed it 👉 lumley.io/blogs/async-...

How to Stub URLSession Responses… or Die Trying The internet is filled to the brim with the gravestones of attempts to stub URLSession responses. As something of a strange holdover from the Objective-C days, URLSession is notoriously hard to…

so i wrote a thing about stubbing URLSession based on a 'trick' i discovered the other day jellystyle.com/2025/09/stub...

Swift 6.2 Released We’re excited to announce Swift 6.2, a release aimed at making every Swift developer more productive, regardless of where or how you write code. From improved tooling and libraries to enhancements in ...

www.swift.org/blog/swift-6...

iOS Dev Tip 💡

Easily monitor the device’s thermal state to optimize performance during overheating.

→ learnandcodewithenid.com

Making this argument and then hanging the entire load on TRY is fucking hilarious:

💡Starting with iOS 18.0, you can create mesh gradients in SwiftUI using MeshGradient.

→ learnandcodewithenid.com

FaviconFinder by @will-lumley.bsky.social is awesome!

github.com/will-lumley/...

Thank you for the shoutout @weijianduan.bsky.social! I’m really glad it’s managed to help you :)

Adjust the intensity of colors in SwiftUI views Lighten or darken colors in SwiftUI views using the brightness(_:) modifier.

There is a convenient brightness(_:) modifier in #SwiftUI that can be used to adjust the intensity of colors in our views. We can lighten the colors by passing it values from 0 to 1 or darken them using negative values:
nilcoalescing.com/blog/AdjustT...

1517, Martin Luther

it’s forbidden in their culture but a vacuum cleaner wants nothing more than to eat it’s own cord

GitHub - Jaennaet/pISSStream: macOS menu bar app that shows how full the International Space Station's urine tank is in real time macOS menu bar app that shows how full the International Space Station's urine tank is in real time - Jaennaet/pISSStream

Why I 💛 the web.

#macOS menu bar app that shows how full the ISS urine tank is in real time. 🛰️🚽

Yurnining to check this out.

github.com/Jaennaet/pIS... #Swift

*click* React Native. *click* Flutter. *click* .....SwiftUI. *click* GTK. Easy. *click* ......Qt6.

How embarrassing! Maybe it’s just an issue on my machine then 💀

CMD+Space doesn't bring up Spotlight anymore and this has ruined my opinion on macOS and life.

How so?

Completion > perfection

With #swiftlang It's easy to forget that the diff between a point-free and pointed styles of function argument passing is not just syntactic but semantic. It's normal to consider these to be equivalent:
1. [1, 2].map(String.init)
2. [1, 2].map { String($0) }
But we shouldn't forget that: 1/4

Do you know about the take function for the Optional type? It takes the value if it is not nil and toggles the variable to nil.
https://buff.ly/3Zin2Wv

I've always just used GPT-4o, but will give o1 a try after this. Keen to see the difference.

A problematic little #swiftlang pattern I often see is "unwrap-then-nullify" for optional values that hold some temp state. This oft comes up when dealing with local caches or scrollOffsets or in-flight tasks, etc. Forgetting to nullify a value to "reset" state is a common mistake. Use take method.

If “the boy who cried wolf” was a notification

Hypothetically, imagine not knowing Swift Testing doesn't have a built-in timeout function, and then writing a bad unit test and pushing it, going to sleep, and then waking up and finding out you've used all your Github Action minutes for the month. On this second day of the month.
Hypothetically.

Currently working on a Swift project that uses Combine, and because it the year of our lord 2024 I'm using Swift Testing to write my unit tests.

But I was struggling with covering my Combine code with Swift Testing.

Here's how I managed to solve the problem!

lumley.io/blogs/swift-...

#iOS #swift