4 ms·
Not at all. You shouldn't be updating the interpreter unless you have to, and then it should be done through your distro's package management and standard upstr
by peterwwillis 14y ago
Not at all. You shouldn't be updating the interpreter unless you have to, and then it should be done through your distro's package management and standard upstream path.
The OP seems to think it's a good idea to upgrade his production code to the newest stable interpreter just because it was released. This is a recipe for disaster. Sometimes there are just hidden bugs you don't see until a weird use case blows up your code, and thorough stress testing should be performed after the unit testing to ensure no major surprises after upgrade.
The best rule for keeping your software stable is: don't change anything.
- jleader 14y agoYour rule ("don't change anything") is also an argument for never adding features! There's a tradeoff here that you're glossing over. Given that each newer version is presumably some amount better than the previous one, eventually the benefits of upgrading will outweigh the costs, at least if you're going to continue making changes to your software. I don't think chromatic was saying "everyone should immediately upgrade to the latest version of Perl". I think he was saying "upgrading to the latest version of Perl isn't as scary/costly as some people think; I did it, and here's my experience." Also, keep in mind that sometimes there are hidden bugs in the old version, too. My employer just ran into a problem with the de-allocation of deeply nested structures being implemented inefficiently in Perl 5.8 (which has been in production for close to a decade); the bug was fixed in 5.14.
- chromatic 14y agoThe OP seems to think it's a good idea to upgrade his production code to the newest stable interpreter just because it was released. You're putting words in my mouth and knocking down the resulting strawman. I upgraded for Unicode and performance improvements.