4 ms·
That’s not really fair. For example Go programs written in v1.0 are still mostly compilable (the few tweaks you do need to make aren’t substantial). Rightly or
by laumars 5y ago
That’s not really fair. For example Go programs written in v1.0 are still mostly compilable (the few tweaks you do need to make aren’t substantial).
Rightly or wrongly Apple very much decided Swift should take a different approach to backward compatibility.
- dehrmann 5y agoYou're always rolling the dice with new languages; Go just happened to be mostly compatible. If you want something that will compile in 20 years, pick something with a track record.
- mst 5y agoMy perl5 version 8 code still runs perfectly on version 34, and for all people's (often valid) dislike of perl still helps a lot of companies make a lot of money. That wasn't the point I was trying to make in that particular comment though.
- laumars 5y agoMost languages offer some guarantee by the time they hit version 1, let alone 2. Take Python for example, v2 took a decade to deprecate. Swift is the edge case on this one. Not the norm.