3 ms·
About goddamn time. Now let's take care of PHP <= 7 and Node <= 8 and us sysadmins can stop living a foot in a decade ago and a foot in today.
by pluc 9y ago
About goddamn time. Now let's take care of PHP <= 7 and Node <= 8 and us sysadmins can stop living a foot in a decade ago and a foot in today.
- smt88 9y ago> Node <= 8 Great! Mostly no problem. The backwards-incompatible changes are few and seem to rarely be used in the projects I've seen. > PHP <= 7 Totally different story. PHP does upgrade slowly, but many of the backwards-incompatible changes are almost impossible to detect without 100% code coverage. A lot of legacy PHP < 7.x code bases are also going to be lacking perfect coverage. That said, I think bespoke PHP is less common than people think. The WordPress/Drupal/whatever installations are major drivers of the usage numbers for PHP.
- foobarbazetc 9y agoWe upgraded our bespoke, massive php5 codebase to php7 in a week. The much bigger upgrade was 4 to 5. We have something like 6 custom C extensions and that was a huge pain. php7 is a great language though. Worth the pain.
- smt88 9y agoI believe you did that conversion and that it worked for you. I still don't think it's a slam dunk when you're talking about a stable, production product that can't have errors. It's almost impossible to do the conversion with static analysis alone, unless you know something I don't.
- apple4ever 9y agoHERE FREAKING HERE
- dang 9y agoWould you please not post unsubstantive comments to Hacker News? https://news.ycombinator.com/newsguidelines.html https://news.ycombinator.com/newsguidelines.html