4 ms·
I'm curious what a good life time length should be to be considered 'stable'. Allowing your code base to run ok for 10 years, 20, 30 without change. You are ta
by FrustratedMonky 3y ago
I'm curious what a good life time length should be to be considered 'stable'.
Allowing your code base to run ok for 10 years, 20, 30 without change.
You are talking Cobol type situations where the rest of the industry has moved on, and now your are stuck. So each individual has to judge jumping ship and migrating their systems.
Even Python took the leap and did a major revision that broke everything. But guess it had to be done.
- binary132 3y agoThe Python 3 upgrade nightmare was a big mistake. I’m not saying I know the right way, but just because they did it that way doesn’t mean they had to and should have.
- baq 3y agoIt was, but the language as it was in 2 was reaaaaaallly not XXI-century ready. They could ship both interpreters and communicate with RPC for all I care as long as shit still worked. Though to be fair I haven’t written a single line of Python 2 for about 10 years now.
- bmicraft 3y agoIt did break everything, but I'd hardly call it a mistake. Python3 is more popular than its predecessor ever was. It was very painful for many people, yes, but it doesn't seem to have hurt the language much if at all.
- binary132 3y agoJust because it worked out doesn’t mean it was fine and the way things should be. There are definitely better ways.