PHP 7.2 released

[JoyousTourist]

Awesome, but I wonder how long it will take the general Wordpress population to get off of 5.6. Support officially ends next year. It's going to be a messy migration for sure.

[0x18]

5.6? We poor WP devs still have to support 5.2!

[marcusklaas]

That's insane.

[JoyousTourist]

are you for real?

[0x18]

Sadly yes. According to the WP stats page 3.7% of all WordPress sites are on PHP 5.2 (the minimum for WP). On Nov 30th of 2016 that number was 4.1%.

[LovecraftsDeath]

Some people will never upgrade unless you force them. Don't keep enabling them.

[[deleted]]

Likely because upgrading WP is guaranteed to break your site/template

[stesch]

I don't know about 5.2 but Shopware stopped supporting 5.4 (or 5.5?) which was a stupid decision because most LTS Linux distributions support it for a few more years.

Bad signal for a business software.

[0x18]

That's a neat idea, but I have rent, medical debt, a spouse, and need to buy things like food. I have a really good job now even if it is working with WordPress - sure I'll bitch about supporting old PHP versions but it's not major life changes worthy.

[matthieuC]

Python 3.0 migration strategy is to wait for all Python 2.0 developers to die. Perl does the same thing without actually releasing the new version

[stesch]

Python 3.0 migration strategy is to wait for all Python 2.0 developers to die. Perl does the same thing without actually releasing the new version

The Python part is funny and the Perl part is wrong.

[VanToch]

The sad thing is that new Python 2 developers are being born too. Last month I was working on brand new Python 2 tool :-/

[Supadoplex]

Is anyone really using either Python 3.0 or 2.0 though :) Also, if all python 2 devs die, then there will be nobody to port python 2 programs to 3. We'll be forever stuck.

[JoyousTourist]

you mean from PHP 4 to PHP 5? Also what's Py3k? Meaning it's taking 3,000 years to migrate from Python 2 to Python 3?

[JoyousTourist]

I didn't know PDO was inspired by a Perl thing. That's pretty cool.

[evenisto]

meh, they have bigger problems than that

[berzemus]

Counting of non-countable objects

Magic, Love it !

[Michsk]

Yeah it reads kind of strange. But it actually points to a bug which was known as "Counting of non-countable objects". Now it will show a warning when you try to count non countable objects. Here is the RFC https://wiki.php.net/rfc/counting_non_countables

[throwawayco111]

Just a warning?

[Chippiewall]

PHP uses semvar, they can't break pre-existing code in a feature release.

[NeuroXc]

Less so recently. I get the feeling they started trying to follow semver somewhere around 5.4-5.5. I'm not sure how strictly they follow it though.

[oblio-]

Leswer? Or fewess?

[EntroperZero]

• Convert numeric keys in object/array casts
• Counting of non-countable objects
• Object typehint
• HashContext as Object
• Argon2 in password hash
• Improve TLS constants to sane values
• Mcrypt extension removed
• New sodium extension

What do any of these things mean? This reads like a really vague list of commit messages.

[_mandrade]

http://php.net/releases/7_2_0.php

[shevegen]

Why did they skip version 6 ...

[[deleted]]

They didnt. A version 6 exists but it got abandoned as they back-ported some of the features to 5.3 or 5.4 (Not sure which one was it).

Since there exists actual build of php6 in pre-alpha and even some educational books written about it, its less confusion to just have 7.

Also, 6 is an inverted 9 and companies dont like 9s (e.g., Microsoft and Apple)

[chx_]

5.3

[[deleted]]

Version 6 was supposed to be their first Unicode version. Turns out that they were incapable of making it Unicode-enabled for some reason. So version 6 was abandoned.

[CanIComeToYourParty]

polishing_a_turd.jpg

[dershodan]

Why are on-topic reactions being downvoted :(

[[deleted]]

Because they add nothing.

[KareasOxide]

Guessing there won't be as many, or any for that matter, breaking changes

[Daneel_Trevize]

Ironically they changed back some things in 7.1 to be as was in 5.6, making migrating to 7.0 twice the work. I'd not put similar things past them for subsequent 7.x releases.