3 ms·

I thought they were pretry clear about why churn was bad: - Many examples are older, and don't compile anymore. - Code maintenence costs increase for long ter

I thought they were pretry clear about why churn was bad: - Many examples are older, and don't compile anymore. - Code maintenence costs increase for long term "write it and forget it" code. I don't have a hrose in this race, but when I heard Swift was making breaking changes, I had an immediate negative reaction.

Grustaf 9y ago
How else could it be improved? The alternative would be to work on it in house for a few more years and only then release it to the world. I think it’s much better to let it be used by millions of developers in real apps and learn from that experience. Migrating code to newer versions is seldom a big problem, and it’s even smoother now when you can run several versions in the same app.