> I feel like it's really lame that its Swift version 157 or whatever and they still don't have a stable async/concurrency story besides callbacks.

It is frustrating, but it seems like they are finally getting there. It’s frustrating since a language like Go had a good concurrency model almost from the start. But Go had different constraints and arguably has less surface area to cover.