3 ms·
> I think a big reason why the python 2 to python 3 transition was so painful was a lack of static typing. And I'll add compilation vs interpretation to this.
by Jtsummers 6y ago
> I think a big reason why the python 2 to python 3 transition was so painful was a lack of static typing.
And I'll add compilation vs interpretation to this. I have, on a couple of occasions, had to update Java or C# code from one version to a much newer version. This meant that deprecated features were often used (more an issue with the Java cases). Thanks to actually compiling the code and the static typing, most of the things I needed to update/change were apparent from the start. This didn't mean they were good "modern" versions of the program, but they were functional and operational and could interact with newer Java and C# code bases properly with only a week or two of effort.
The same was true when a library was changed in a breaking way (at the interface level). Of course, you still need tests when semantics of the library change (like it returns the same type, but with different meanings), but that's usually well-documented.