Let’s avoid going too deep down the rabbit hole of discussing whether this thread itself should continue. It’s too meta. The mods can decide that for themselves, without members telling them which threads should/should not continue.
Despite the harsh tone in this thread, it is the reality of the situation. Apple wants developers excited to create apps for their platform, especially this week with WWDC going on.
A couple years ago when SwiftUI came out and had the iOS13 requirement, many of us groaned. It looked like amazing technology but we knew it would have to wait. Now, the same thing is happening with the next paradigm shift of Swift. We are constantly having new tech dangled in front of us on a stick, and it's frustrating not being able to reach out and grab it. Rather than being excited this week for WWDC I find myself not wanting to watch most of it.
This isn't a new problem though, any old-timer Android developer remembers much of the same happening with Google, like finally getting Java8 support and the Android Support Library. I'm sure we can find a similar path forward on iOS.
Anyway, I do appreciate the Apple engineers responding throughout this thread and making us feel heard. The frustration here is from us wanting to use your tech very badly, which is a good problem to have.
Personally, I agree. For me, it's emotionally painful to see such negativity from the community after working hard to help make Swift Concurrency happen. I'm surprised to see people injecting ulterior motives into the discussion, making wild suggestions to the Swift team to rewrite or reimplement the whole feature (or the entire system stack), and starting a petition, all because Swift concurrency isn't compatible with their project's minimum deployment target right now.
OK I'm locking this thread now, because the majority of new posts are off-topic or inappropriate and getting flagged, and I really don't want to mess with people's trust ratings by approving/rejecting them. As Doug and Ted have said, we hear everyone who is enthusiastic to adopt the new features loud and clear, and we'll keep you updated on our findings as we progress.
For those interested in the technical implementation challenges, I recommend posting focused questions to the Compiler Development topic – but please be understanding about the time it takes to produce responses explaining these details.