.@mjtsai I think the problem you identified in your blog entry permeates Swift - trading predictable runtime perf for "the correct way".
@mjtsai It's a problem of "magic" code too. There is a lot of it built into language - auto closures and return overload are the worst.
-
@nuoji Yeah, one thing I've noticed is that it seems to be harder to read other people's Swift code than other people's Objective-C.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
Christoffer Lernö
Michael Tsai