And most importantly, a HUGE Thank You to the many individuals and organizations who helped host the main PHP website over the years.
Effective today, the PHP project has ended its volunteer mirror program. All users of PHP will now be accessing https://php.net/ sites directly from project servers and via CDN.
New RFC for arrow functions / short closures: https://wiki.php.net/rfc/arrow_functions_v2
Uses fn($x, $y) => $x * $y syntax and implicit by-value binding of variables. The RFC has a detailed discussion on why we're unlikely to get the more popular ($x, $y) => $x * $y syntax...
Happy (late) Valentine's Day from @official_php https://twitter.com/github/status/1096208730281181185
10/10: The only community of users that likely interacted with a go-pear.phar file is someone that has PHP already and wanted to manually install PEAR themselves, and chose to manually download go-pear.phar to do it. Once PEAR is installed, go-pear.phar would not be used again.
9/10: If you manually installed PHP and it included a PEAR installation during its installation, it is hugely unlikely that go-pear.phar was pulled in for that task (it uses install-pear-nozlib.phar instead)... and even more unlikely that you would have used it on that system.
8/10: If you installed PEAR on your Linux system using your distribution's package management tool, it is hugely unlikely that go-pear.phar was included with it... and even more unlikely that you would have used it on that system.
7/10: If your system has PHP and PEAR preinstalled, it is hugely unlikely that go-pear.phar is on it... and even more unlikely that you would have used it on that system.
6/10: The largest misunderstanding we see in the wild is thinking that go-pear.phar *is* the PEAR installer program itself, and that it's what you use over and over again to install various PEAR packages. This is *not* the case.