Re:No-op statements syntactically valid only since Python X.Y
by dspillett on Monday June 06, 2022 @03:34AM
(#31638070)
My main memory of perl (I used it for CGI and local CLI tooling back in the day) was that it was usually very terse, to the point of being a write-only language. I learned an important lesson with it: the more clever you feel writing code, the more you are likely to hate maintaining it after a few months away!
[ Parent
| on HN ]
Re:No-op statements syntactically valid only since Python X.Y
by xyzzy123 on Monday June 06, 2022 @05:36AM
(#31638597)
There was a long time period (IMHO good few years in early 2000s) where Python looked better on paper but Perl was still better for production.
All the Perl libraries for doing certain things (db access, web stuff, process management) were "actually battle tested" and worked well even if they were utterly unreadable. Python looked a lot nicer but when you tried to do any real work with it everything seemed to leak memory or give you continuous paper cuts - and it was a lot slower.
I made the switch to Python eventually but it took a while.
Re:No-op statements syntactically valid only since Python X.Y
by dspillett on Monday June 06, 2022 @12:32PM
(#31642587)
> (IMHO good few years in early 2000s)
That tallies with when I was using Perl (late 90s / early 00s). Python was very much on the up in that time but I didn't feel compelled to switch, then DayJob and personal projects took me away from such thing completely (DayJob was Windows/VB6/IIS/ASP based, home web stuff went PHP for a while and admin stuff to Bash).