Donny WalsNov 2, 2024

As much as I enjoy using Swift Concurrency Combine is still the better way to observe state IMO. AsyncSequence works well for some cases but the ergonomics of Combine are better at this point in time.

Learning Combine is more fun than you might think https://practicalcombine.com/

Practical Combine - Donny Wals

Learn Combine from the ground up with a solid theoretical foundation and real-world examples of where and how Combine can help you move from writing imperative code to writing reactive code that is flexible, clean and modern.

Practical Combine - An introduction to Combine with real examples
Show threadMartin Höller
@donnywals I also don’t understand the hate Combine often gets. Yes, Apple hasn’t updated it in a while, but that doesn’t automatically deprecate it.
Nov 2, 2024 at 1:34pmIceCubesApp
Show threadMartin HöllerNov 2, 2024
@donnywals for example in a big project I’m working in we observe a hardware entity that emits many different datapoints. Everything is essentially a huge, Combine publisher that is used all over the app. The various parts of the app then can observe the whole flow or just the parts they are interested in. Combine really is the perfect tool for that.
Show threadJaanus KaseNov 4, 2024

@martinhoeller @donnywals AsyncSequence would work fine for this IF it supported multicast, which it currently does not

You can filter async sequences the same way as Combine publisher outputs, and I think Apple is nudging us to eventually do that

But yeah, lack of async sequence/stream multicast (broadcast streams with multiple subscribers) is a showstopper right now