top | item 38229812 (no title) TeddyDD | 2 years ago But then you have to keep old interpreter installed and you won't benefit from improvement in new versions of the interpreter.Your old Go code not only will work with new versions of the compiler - it probably will run faster. discuss order hn newest cpuguy83|2 years ago This is incorrect. Go does make breaking changes all the time. I've seen it. I've helped maintain stdlib forks because of breakages.Still compiles is not the same thing as "works". usrbinbash|2 years ago I'm certainly not gonna defend Python here, but...>But then you have to keep old interpreter installed...thanks to `pyenv` that really is a solved problem, even outside containerized environments. unknown|2 years ago [deleted]
cpuguy83|2 years ago This is incorrect. Go does make breaking changes all the time. I've seen it. I've helped maintain stdlib forks because of breakages.Still compiles is not the same thing as "works".
usrbinbash|2 years ago I'm certainly not gonna defend Python here, but...>But then you have to keep old interpreter installed...thanks to `pyenv` that really is a solved problem, even outside containerized environments.
cpuguy83|2 years ago
Still compiles is not the same thing as "works".
usrbinbash|2 years ago
>But then you have to keep old interpreter installed
...thanks to `pyenv` that really is a solved problem, even outside containerized environments.
unknown|2 years ago
[deleted]