I enjoy reading Marcel's Swift contrarianism (even if I don't always entirely agree with it). I work with Swift and ObjC on a daily basis. I remember the entire

I enjoy reading Marcel's Swift contrarianism (even if I don't always entirely agree with it). I work with Swift and ObjC on a daily basis. I remember the entirely appropriate skepticism that we in the Apple ecosystem had for ObjC when it was the main language. And I'm getting more and more tired of that healthy skepticism having turned into pointless bashing, accompanied by tall frosty pitchers of Swift kool-aid. No language is perfect, and it's important to be cognizant of the tradeoffs and flaws. There's no denying that Swift is a powerful language in many ways. But there's also no denying that the chosen means to that power has costs. The most obvious is a lot of complexity, both essential and non-essential. Which brings us back to the article and the peculiar way multiple trailing closures ended up being integrated.