3 ms·
Yes, I understand that the conversion is in some ways more difficult because there's a larger legacy code base. However, the conversion has already been extend
by melling 10y ago
Yes, I understand that the conversion is in some ways more difficult because there's a larger legacy code base. However, the conversion has already been extended 5 years:
https://news.ycombinator.com/item?id=7581434 https://news.ycombinator.com/item?id=7581434
A decade long conversion is fine if that is what the community wants. There are certain drawbacks to this.
I simply like the aggressiveness that Apple has taken. The community can put "all its wood behind one arrow".
- hota_mazi 10y agoI like the aggressiveness too but it's pretty common for very young languages because the cost is so low. Swift is not doing anything new there.
- melling 10y agoReally? I've been programming for almost 35 years and I can't think of many languages that made such big changes. Java, for example, is still compatible with 1.0.
- hota_mazi 10y agoJava is one language among hundreds that have come out these past twenty years.
- melling 10y agoYes, I know that. You could provide your examples of some other popular languages that we all know about. Sure, it's easy to change a language no one uses, but when you've got hundreds of thousands of users, it's much harder.