I don’t want to put words in anyone’s mouths, but PHP 5.6 still receives 
security support — and will be until December 31, 2018. And 31% is nonetheless 
a rather sizable number (a little under 1 in every 3 PHP developers use 5.6). 
As a de facto standards body, I think the FIG should follow the core team in 
this.

Once the time comes, in a year and four months, the FIG definitely should 
update all non-depreciated PSRs with PHP 7 gloriousness. Funnily enough, PHP 
7.0 actually will be EOL’d shortly before 5.6, so we can even go directly to 
void return types and all that goodness.

Just my 5 cents though. :)

John

On Aug 3, 2017, at 8:17 AM, Adrien Crivelli 
<[email protected]<mailto:[email protected]>> wrote:


On Wednesday, 2 August 2017 19:01:34 UTC+2, Woody Gilk wrote:
> This would require >= PHP 7

That's a non-starter. There are plenty of people stuck on PHP 5.x for various 
reasons and I don't want to shut them out.

PHP 7+ was more than 
53%<https://seld.be/notes/php-versions-stats-2017-1-edition> of composer usage 
last May, and PHP 5.6 only at 31%. This PSR is yet to be released and by the 
time it is those numbers will be even more in favor of PHP 7. Nowadays I would 
rather see PSR pushing innovation on new tech (including language syntaxes), 
rather than being stuck in the past and spending more time to deal with 
compatibility than what it is worth.

Also this specific PSR is all about new way to do things. I don't think future 
adopter would be the guys who are stuck with PHP 5, but rather the one who are 
already on PHP 7.1 today.

As I am sure you are aware, major projects are moving to PHP 7 only. Doctrine 
will require 7.2<https://github.com/doctrine/doctrine2/issues/6529>, ZF3 
requires 7.1<https://framework.zend.com/blog/2017-06-06-zf-php-7-1.html>, 
Symfony 4 will require 
7.1<https://twitter.com/fabpot/status/851558576770252800?lang=en>, TYPO3 8 
requires 7.0<https://typo3.org/download/>, to name only a few.

--
You received this message because you are subscribed to the Google Groups "PHP 
Framework Interoperability Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
[email protected]<mailto:[email protected]>.
To post to this group, send email to 
[email protected]<mailto:[email protected]>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/php-fig/715fe4dd-6c95-4964-9f9c-e725e9752dd9%40googlegroups.com<https://groups.google.com/d/msgid/php-fig/715fe4dd-6c95-4964-9f9c-e725e9752dd9%40googlegroups.com?utm_medium=email&utm_source=footer>.
For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups "PHP 
Framework Interoperability Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/php-fig/4EA49880-812B-4C96-9CB7-109CBFD1150B%40buffalo.edu.
For more options, visit https://groups.google.com/d/optout.

Reply via email to