Are there any issues running PHP 5.6-based code on a PHP 7.x VM?
Depends on the x, but more importantly, depends on the code.
PHP 5 and 7.0 end of life
41–50 of 122 posts
Re: PHP 5 and 7.0 end of life
#42Are there any issues running PHP 5.6-based code on a PHP 7.x VM?
> PHP7 support - String class must be renamed, it is reserved in PHP7
[0]
Re: PHP 5 and 7.0 end of life
#43Earlier quoted context omitted.
ColdFusion and ActionScript
ColdFusion's still around. https://www.adobe.com/products/coldfusion-family.html
I miss ColdFusion. I really liked the idea of a tag based server side language. It will never have the power or expressiveness of other languages but for raw productivity of producing very simple dynamic apps with an incredibly low bar to entry for new/non-programmers, nothing else was even close.
Re: PHP 5 and 7.0 end of life
#44Yeah, yeah. Go tell that to my 10x php self-taught guy who's still running php 5.4 on a windows server 2003 in a wamp installation. He upgraded the bundled mysql with mariadb last year by dropping the executable in the folder (edit: just checked out, and the drop-in has been reverted back to mysql 5.0 because the upgrade path is impossible because apache 2.2). And of course this in-house guru for anything that happen…
Besides the "doesn't bother updating the passwords" point, this sort of "it's old so let's change it" attitude is unfortunately so pervasive in the software industry and I find it massively irritating because it's the same reason why a lot of software has gotten increasingly unstable over time. Instead of making only fixes and bringing a platform towards maturity they do the exact opposite, adding plenty of new bugs…
"it's old so let's change it"
That's very rarely the thought process in the real world when you're dealing with a production system though. Most developers who have the seniority and experience to make the call to upgrade something aren't just upgrading for the fun of it. It's more like...
"it's old and hundreds of security patches and performance improvements have been released in versions that have come along since it was current, and the core developers aren't supporting this version any more so we're in for a world of hurt if anything goes wrong, and we have the bandwidth to fix this problem right now where we might not in the future so let's change it"
Re: PHP 5 and 7.0 end of life
#45Earlier quoted context omitted.
ColdFusion's still around. https://www.adobe.com/products/coldfusion-family.html
I miss ColdFusion. I really liked the idea of a tag based server side language. It will never have the power or expressiveness of other languages but for raw productivity of producing very simple dynamic apps with an incredibly low bar to entry for new/non-programmers, nothing else was even close.
With ColdFusion 5 they did let you out of the strict tag box slightly, with the cfscript tag:
https://helpx.adobe.com/coldfusion/cfml-reference/coldfusion...
Re: PHP 5 and 7.0 end of life
#46Yeah, yeah. Go tell that to my 10x php self-taught guy who's still running php 5.4 on a windows server 2003 in a wamp installation. He upgraded the bundled mysql with mariadb last year by dropping the executable in the folder (edit: just checked out, and the drop-in has been reverted back to mysql 5.0 because the upgrade path is impossible because apache 2.2). And of course this in-house guru for anything that happen…
Besides the "doesn't bother updating the passwords" point, this sort of "it's old so let's change it" attitude is unfortunately so pervasive in the software industry and I find it massively irritating because it's the same reason why a lot of software has gotten increasingly unstable over time. Instead of making only fixes and bringing a platform towards maturity they do the exact opposite, adding plenty of new bugs…
FWIW, I think the concern with "doesn't bother updating the passwords" was with respect to recovering from a hacked joomla install, not about an aging password management scheme.
Re: PHP 5 and 7.0 end of life
#47Somebody should fork PHP 5.6. There is a lot of Software still depending on it and it is unrealistic to expect companies to migrate millions of lines of third party code to PHP 7.
I really hope nobody does this. OS vendors backport security vulnerabilities, and that should be it.
Like the other commenter said, PHO 5.6 to 7 upgrade isn't that hard. If it is, there's a very good chance they are doing something devastatingly wrong (like using mysql_ extension).
Re: PHP 5 and 7.0 end of life
#48Yeah, yeah. Go tell that to my 10x php self-taught guy who's still running php 5.4 on a windows server 2003 in a wamp installation. He upgraded the bundled mysql with mariadb last year by dropping the executable in the folder (edit: just checked out, and the drop-in has been reverted back to mysql 5.0 because the upgrade path is impossible because apache 2.2). And of course this in-house guru for anything that happen…
Besides the "doesn't bother updating the passwords" point, this sort of "it's old so let's change it" attitude is unfortunately so pervasive in the software industry and I find it massively irritating because it's the same reason why a lot of software has gotten increasingly unstable over time. Instead of making only fixes and bringing a platform towards maturity they do the exact opposite, adding plenty of new bugs…
I'm well in to repairing and longevity, but that 80yo fridge is going to be inefficient and badly thermally insulated I imagine (and if it's electric it's probably hazardous too).
Upgrading isn't just about shiny-shiny, and keeping old stuff isn't always best.
Re: PHP 5 and 7.0 end of life
#49For a second, after reading the title, I thought PHP as a whole was end of life. That'd be fun. Which also made me think - does anybody know an example of a widely used programming language that voluntarily discontinued?
I had the same thought. I was like that's weird that such a popular language has reached end of life. Then I clicked the article. I'm curious about your question as well.
Re: PHP 5 and 7.0 end of life
#50Earlier quoted context omitted.
Magento is not exactly known for well written code, actually it is full of anti patterns and antiqued practices. PHP 7 was released in 2015, and if authors of those millions of lines of code can't be bothered to upgrade then probably their code should not be used.
> Magento is not exactly known for well written code As are many/most PHP 5.6 projects > Probably their code should not be used. In reality it is - unfortunately. And many smaller companies don't have the capacity to change.
Agreed with both statements, but things need to move forward.