2 ms·
> By comparison, I never experienced such churn with perl. I literally have 20+ years old perl scripts, usually doing one single thing (many of them) still wor
by ajsnigrutin 4y ago
> By comparison, I never experienced such churn with perl.
I literally have 20+ years old perl scripts, usually doing one single thing (many of them) still working on new machines without issues.
I've rewritten some stuff from python(2) to perl (instead of python3) because i was unsure when a new rewrite for whatever reasons...
Now, more python stuff needs fixing, while perl still works.
- namrog84 4y agoYour kinda comparing simple basic api in perl vs likely more complicated python code here aren't you? If you had a set of single simple python functions maybe they wouldn't have broke as much if at all?
- ajsnigrutin 4y ago> If you had a set of single simple python functions maybe they wouldn't have broke as much if at all? Like (python 2): print "hello world!" ? ( https://docs.python.org/2/tutorial/introduction.html https://docs.python.org/2/tutorial/introduction.html )
- camdenreslink 4y agoPython 3 came out 14 years ago, and changing the syntax of one function wasn’t even a big deal then. Literally a 10 minute code search to fix a project. It might be time to move on…
- ajsnigrutin 4y agoIt was literally months to fix every change in every project and to fix all the issues coming from that. ("print" wasn't the only change in 2->3) Our codebase is was (and is) old, but the forced change came recently, when ubuntu decided to remove python 2 support (ubuntu 20.04?). And when ubuntu decides that they want python >=3.12 as the only version installed, this means another change and more work to fix stuff that worked just fine.
- musicale 4y agoSomewhere Larry Wall is laughing (and/or crying.)