4 ms·
Really? I even ported 2.7 code back when 3.6 got good, and it was all far simpler than I had dreaded. I might be not as eager as some to learn new features tho
by brnt 3y ago
Really? I even ported 2.7 code back when 3.6 got good, and it was all far simpler than I had dreaded.
I might be not as eager as some to learn new features though, but I am also not so conservative that I won't do things some new way, especially if the old way is being deprecated (but so far warnings have always given me plenty of heads up).
Quite the opposite, I like Python as much as I did when we first met. Nothing is without warts, but they are rarely really problematic for me in Python.
- medo-bear 3y agoIf your energy levels drop, or you lose interest, ports will become harder. When you write code that has a short life span none of this matters. But when your software has a several year or decade life expectancy it will matter. Also economics plays a role. If we have a real economic downturn in IT bit rot will become a huge problem for many small businesses.
- brnt 3y agoIf any effort is too much, you're basically stuck on a very select set of dead-ish languages or dialects thereof. But I'm not sure that's a more viable approach then using a language that is still pretty great about backwards compatibility.