Live data from Hacker News

PHP 5 and 7.0 end of life

hackertarget.com

21–30 of 122 posts

Re: PHP 5 and 7.0 end of life

#21

Note that multiple Linux distributions will still be supporting it, in some cases for a very long time after.

Exactly. These EOL dates aren't really helpful in a world where most people just use a handful of distros. WordPress keeps sending the same unhelpful message and I hate it.

Just the other day, a somewhat technical client of mine called me to ask if his PHP 7.0 installation has gaping security holes. I said no, you're using Ubuntu 16.04 LTS, you'll be fine until April 2021. If you force an upgrade now, you might run out of support even earlier.

My go-to version for production right now is PHP 7.2. I'm going to ignore all warnings about its EOL until 2028, when support for Ubuntu 18.04 runs out. Wait a sec, add another year for RHEL/CentOS 8 which is also going to support PHP 7.2 for the next 10 years. PHP 7.2 is going to outlive a whole bunch of future versions.

Re: PHP 5 and 7.0 end of life

#22

Yeah, 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’ve just finish (yesterday night) to move old websites I host from a PHP 5.2 VM to 5.6

Some of them are more than 10 years old !

And as they represents a good share of my profits, I can’t dump them.

I think I saw a Joomla 1.5.

Those clients don’t want to pay someone to upgrade or redo their site.

There are several intranets that will not support PHP 7 because they use the old mysql_ functions...

So even I loose a lot of my semi-passive incomes, or I continue to tell them on a regular base that they should upgrade.

(For the anecdote, there were around 40 websites before I alerted my clients in April. 5 of them have migrate to last versions of Wordpress or joomla. 35 more to go...)

Re: PHP 5 and 7.0 end of life

#23
post #11

Earlier quoted context omitted.

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.

In theory, yes. However as the Germans say "the devil is in the details". The .patch file for magento 1 for PHP7 compatibility is around 1.9 MB (iirc)! In the standard PHP5 project you have literally millions of lines of third party code, that one shold not touch with a stick. Are you really going through all of this code to check if something is maybe going to break at runtime? What if the legacy project has 0 tests…

Magento 1.x reaches end of life June, 2020 (if they don't extend it... again).

I'd be more concerned about having a Magento 1 site in the wild, than the upgrade path to PHP 7.

Re: PHP 5 and 7.0 end of life

#25
post #17

Yeah, 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…

The issue with PHP is devs like that guy.

Indeed. I'm not a fan of PHP but I think a big part of its poor reputation is from this kind of developer.

I'm still maintaining some code written by someone like this - though it's been mostly replaced by a new rails app I've developed.

Re: PHP 5 and 7.0 end of life

#26

Yeah, 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…

is that 5.4/2003 setup online or only intranet ?

Re: PHP 5 and 7.0 end of life

#27

Yeah, 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…

is that 5.4/2003 setup online or only intranet ?

Online. And there is a bunch of intranet stuff deployed on it and accessed through hosts file on employee's machines.

Re: PHP 5 and 7.0 end of life

#28

Yeah, 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".

You should know it means his understanding on 7.x is not stable enough.

Re: PHP 5 and 7.0 end of life

#29
For 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?

Re: PHP 5 and 7.0 end of life

#30
post #19
post #18

Earlier 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.

Those smaller companies will find out maintenance is costly either way.
Post reply on HN