And thus grows the ever increasing list of reserved keywords in Swift. All for a badly designed feature. Along with another pile of crap on top, approachable co

And thus grows the ever increasing list of reserved keywords in Swift. All for a badly designed feature. Along with another pile of crap on top, approachable concurrency, that will still work weirdly and be prone to so many bugs and impossible to understand behaviours. Swift's insistence on having NIH syndrome made them ignore all proper concurrency management systems of the past fifteen years. What's that, structured concurrency, Erlang's lightweight processes, Project Loom, goroutines? all better concurrency systems than anything Apple has ever put forward, all publicly available in the form of implementation or research paper years before.