3 ms·
Fast: from C++11 to C++14 to C++17 soon.. The problem is that if you stay on old language versions, you're doomed soon or later (see the world moving to Python
by IloveHN84 8y ago
Fast: from C++11 to C++14 to C++17 soon..
The problem is that if you stay on old language versions, you're doomed soon or later (see the world moving to Python 3.7, Java 11, C#7, Go 2,..).
If you consider then JavaScript, things are moving at speed of light. Today's framework might be ancient in a couple of months (React version??)
- majewsky 8y ago> if you stay on old language versions, you're doomed soon or later (see the world moving to [...] Go 2) Go 2 is notable on that list because the Go developers have already promised that all Go 1 code will continue to compile and work with Go 2. It's not a 2.0, it's more like 1.15 or 1.20. I guess they learned from the Python 2->3 transition.
- int_19h 8y agoIt's not a "learned" thing. Go can pull it off, because it's much younger, and doesn't have so much accumulated cruft. Eventually they will - and then they would either have to make the decision to break compatibility in some future major release - or become the next Java in a sense that there are parts of the language and the library that are warts upon warts, that no new code will ever use, and that confuse new developers, but which are needed for old code to run.