Moaning doesn't help much, but lying to ourselves doesn't help either… it's quite common here that people rave how fast Swift is, and how great Swift performs in server side development, or in AI — but this bubble actually doesn't matter for the rest of the world.
You can give as much hearts as you want to those "this is fine" comments, but when you want to improve, first step should always be acknowledging shortcomings, so that you can decide on which to spend resources in the most efficient way (low effort, high impact).
Luckily, many people who are in charge seem to be aware of the existing flaws, but obviously, there is a strong pressure to focus changes relevant for their employer…
So, when you want to see the real picture, take off the rose-coloured classes and look beyond the ivory tower:
https://docs.vapor.cloud/shutdown/
...
I'm pretty sure someone will come up with "explanations" why each of those links is actually good news for Swift, but I don't think those could convince neutral observers (I'll probably not even respond to flawed arguments).
It's still remarkable how fast the project got traction, but I think the opportunity for Swift beyond Apple passed away; it is really hard to establish a programming language, so maybe focussing on iOS is not that bad.
It would have been really nice if Swift did become the thriving open source project I hoped for years ago, but for the hard reality, you don't even have to look far:
Compared with contenders like Go, it's just incredibly hard to get Swift up and running on you own 