Swift 5 will most likely include async/await
Because whether a language is slow to evolve only makes sense relatively to some baseline rate.
>Technology and it's pace isn't the same as it was decades ago, and I see no reason that we should hold it to the standard of that time.
And yet still, today, popular languages take their time to get features like async/await. Python got it after 3.6 (so 20+ years on), JS only got it in 2017, C++ doesn't have it, Rust doesn't yet have it (it's coming), Java doesn't have it, C++ doesn't have it...
Heck, Golang doesn't have generics and comfortable error checking still...
In my experience, Swift is lacking any particular major improvement over ObjC. It seems like async/await could have been that big step, and Swift probably shouldn't have been adopted until it was in place. Just wasn't worth it.
I realize that's a controversial topic and I know people who love Swift, just from my perspective it was such an enormous cost without enough upsides to justify it.