News for hackers. Stuff that matters.

A comment on Python Deployment Anti-Patterns. Parent comment

Re:Python Deployment Anti-Patterns by chromatic on Monday April 30, 2012 @02:42PM (#3910676)
That said we are at least talking about python, which has had better release QA and backwards compatibility than perl....

I'm curious as to your experience here. I've found that Perl has by far the best backwards compatibility and release QA of the major dynamic languages. What did you encounter?

[ Parent | on HN ]
Re:Python Deployment Anti-Patterns by pconf on Monday April 30, 2012 @11:40PM (#3912895)
We don't use as much perl as we used to but the last upgrade issue was amavisd-new (a Spamassassin wrapper). Spamassassin has perl version issues every so often as well. NetDNS used to introduce new bugs about every 4th revision but seems to have been stable for the past couple of years. GNUmp3d and many audio libraries have non-perl revision-related, backwards-compatibility issues with some regularity.
[ Parent | on HN ]
Re:Python Deployment Anti-Patterns by chromatic on Tuesday May 01, 2012 @02:15AM (#3913258)
That makes sense. XS components (compiled code which uses the Perl API) don't have binary backwards compatibility between major Perl releases.
[ Parent | on HN ]
Re:Python Deployment Anti-Patterns by pconf on Tuesday May 01, 2012 @08:15PM (#3916962)
The audio library incompatibilities were API changes. Amavisd's issues are not binary either but do seem mostly socket related.
[ Parent | on HN ]