Re:Perl and Perl Module Administration in the Modern Era
by mechanical_fish on Wednesday April 03, 2013 @01:32PM
(#5487557)
I don't work with Perl anymore, but the same problem has played out in the Ruby space, with the same conclusions.
Re:Perl and Perl Module Administration in the Modern Era
by kbenson on Wednesday April 03, 2013 @02:46PM
(#5488169)
I think this is the natural state of things for any successful language.
Useful languages will be used.
Used languages will evolve.
Evolution may introduce problems with code written to an older version.
People that rely on older code will have some resistance to newer versions.
A natural friction will arise between those who wish stability in order to maintain, and those who which change in order to evolve.
IMHO if nobody cares about breaking older stuff, that just means that nothing useful has been written yet.
Additionally, there's the problem of perl (python as well for the last decade) being used as glue for many OS-level tools. Have you ever tried replacing the packaged Perl on a n RHEL box? It's not fun. Also, since it's relied on by so much within the distro, the chances they are going to go through the trouble of updating the version and risk problems is very small. On enterprise distros, you are essentially stuck with an out of date Perl before the distro ships, and stuck with it for the long support lifetime.
This is frustrating to the perl community, as anything that requires "new" features faces limited adoption as a significant portion of the community can't run those versions.
That's not to say that packaging perl isn't the way to go. I believe in many cases it is. I also think it depends on your targets. Three webservers does not make the same argument as a farm of boxes. Even so, the ability to easily test and iterate in your dev environments, before committing resources to building packages and pushing them to QA, is a good thing.
Edit: Changed redundant "additionally" to "also" so it wouldn't bother me anymore. :)