2 ms·

So you ding the language because of a suboptimal choice made by one tool for it? The good and bad of Swift is the regular breaking updates. Sure it’s a pain wh

So you ding the language because of a suboptimal choice made by one tool for it? The good and bad of Swift is the regular breaking updates. Sure it’s a pain when things change, but it’s also healthy when they improve, and almost every change has been an improvement. A language as simple as C can slowly grow without breaking existing source code. But it’s also never been able to address its most significant flaws.

dmitriid 6y ago
> So you ding the language because of a suboptimal choice made by one tool for it? I provided 4 different links showing multiple different features in the language I find suboptimal. > Sure it’s a pain when things change, but it’s also healthy when they improve, and almost every change has been an improvement. It's a very dubious statement at the very least. > But it’s also never been able to address its most significant flaws. Can Swift address its flaws even with its breaking changes? So far its been piling on more and more syntax, and continuously breaking its standard library (whose design choices like writing to files from Strings are very dubious)?