On Sun, 2017-10-22 at 05:34 -0500, Larry Garfield wrote: > On Sat, Oct 21, 2017, at 03:19 PM, Tobias Nyholm wrote: > > Hey. > > > > While reviewing PSR-18 I found a suggestion to make our base > > exception to > > implement \Throwable. So, should new PSRs support PHP 7 only or do > > we > > still > > need PHP 5 support? > > > > Like someone said, "PHP5 is dying, just kill it already". I like to > > agree > > with that. But at the same time, I do not what the guzzle/buzz > > community > > to > > choose between implementing this PSR or supporting PHP5.
I think there is a chicken and an egg problem here. If we as the FIG continue to outwardly support PHP 5 backward compatibility, we are potentially hamstringing ourselves for the sake of libraries instead of creating standards on modern code. And if our PSRs are specifically targeted at PHP 5.x, then that allows libraries to stay there longer. Personally, I'd rather see a greater adoption of PSRs that are geared toward making lives easier and making sane standards, but not at the sacrifice of compatibility on non-supported versions of the language. If a library wants to continue to support a non-supported version of PHP... well, then that's on them, whatever their reasoning may be. > > > > I would like the core committee to give me (and other authors of > > new > > PSRs) > > a unified recommendation: Should new PSRs support PHP5 or not? > > > > // Tobias Nyholm > > Naturally we shouldn't be incompatible with older PHP versions "just > because". However, at this point in time if a spec would benefit > from a > PHP 7.0 feature I fully support using it. (7.1 is too aggressive, I > think, but 7.0 shouldn't be.) I'm in agreement with Larry. It's 2017, PHP 7.0 has been out for a good while now, and, honestly, it's well past the time that PHP 5.x was supported. > > Scalar and return types are the most likely feature to trigger a PHP > 7 > dependency since those are the ones that matter most to interfaces, > but > in general, yes, if a spec would be better with PHP 7.0 features, use > PHP 7.0 features. It's 2017, PHP 7 uptake is very good compared to > the > PHP 5 transition, and many many major projects either already require > PHP 7 or will within the next year. And I agree with this as well. Just because PHP7 has static type hinting or other features doesn't mean a spec _must_ use it. I rarely use a bunch of PHP 7 features, but target PHP 7 for new code just in case. > > --Larry Garfield > -Chris Tankersley -- 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/1508693919.22106.41.camel%40ctankersley.com. For more options, visit https://groups.google.com/d/optout.
signature.asc
Description: This is a digitally signed message part
