> Ultimately, though, I need something that solves my problems. My problems aren’t performance. They aren’t type-safety (maybe it’s just me, but I rarely have issues with it and when I do, the time it takes to fix it is far less than the time specifying everything to a tee everywhere else). They aren’t being able to write clever VDLs. For me, it’s writing apps that solve my users’ problems and getting them out in a timely fashion. As it stands now, Swift (at least pure-Swift, or even current Swift as a non-ABI-stable moving target) does not do that for me.

While I feel I understand what you mean by the above, as someone from outside both ObjC and Swift, but with a strong interest in languages, it's still hard to understand what exactly you'd need.

In that sense I read the above more like: "As a long time ObjC developer with an existing ObjC code base, I don't think Swift is improving my productivity." Even to this I could probably come up with some arguments (e.g. better tooling => faster development, less and more explicit errors => shipping faster, faster code => happier customers, etc.)

There are too many facets to this problem to be able to generalize it though. And in the end, I could agree with something like: "for my code base and based on my experience and level of expertise, I don't think Swift brings any major improvements".