PHP 5 and 7.0 end of life
hackertarget.com
PHP 5 and 7.0 end of life
1–10 of 122 posts
Re: PHP 5 and 7.0 end of life
#2Wait what?
PHP 8 isn’t even out yet. How can PHP 7 already be deprecated and not even supported?
Re: PHP 5 and 7.0 end of life
#3Wait what? PHP 8 isn’t even out yet. How can PHP 7 already be deprecated and not even supported?
PHP 7.0 is eol, not php 7.1, 7.2, and 7.3.
Re: PHP 5 and 7.0 end of life
#4Wait what? PHP 8 isn’t even out yet. How can PHP 7 already be deprecated and not even supported?
Article states 7.0 is end of life. 7.X that isn't 0 is not end of life.
Re: PHP 5 and 7.0 end of life
#5Note that multiple Linux distributions will still be supporting it, in some cases for a very long time after.
Re: PHP 5 and 7.0 end of life
#6Yeah, 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 happens on a screen patiently overwrites hacked 1.6 joomla installations by copying over an old copy and doesn't bother updating the passwords.
I am in the process of dockerizing almost everything in sight. There's pain.
Re: PHP 5 and 7.0 end of life
#7Somebody 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.
Re: PHP 5 and 7.0 end of life
#8Yeah, 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…
I feel your pain. Yesterday client's "wp developer" asked me to downgrade from 7.2 to 5.6 because "7.x is not stable enough".
Re: PHP 5 and 7.0 end of life
#9Somebody 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.
Honestly I don't think that's a bad idea.
Where I work I develop a web app that's written in Rails, and it's replacing a legacy PHP 5.6 app. Now here's the thing - no-one is using the PHP app anymore, but we do still have some old data on there that we made a decision not to port over to the new app. At the time it seemed like it wouldn't be a problem - just keep an old version of the app up for those who need to view historical information.
Now I'm thinking I'll have to set aside some time to either port it to PHP 7 (which isn't really a priority) or come up with something else for viewing that historical data.
Re: PHP 5 and 7.0 end of life
#10Somebody 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.
PHP 7's changes shouldn't affect most 5.6 code, and the code that is affected should not be difficult to fix. It's not supposed to be a Python 2/3 situation.