3 ms·
Oh well we are about to break most of said 10 year old web sites. Particularly, PHP 8.1 has some changes that low key force people to update, such as the use o
by Ayesh 5y ago
Oh well we are about to break most of said 10 year old web sites.
Particularly, PHP 8.1 has some changes that low key force people to update, such as the use of return types when extending a built-in classes (https://php.watch/versions/8.1/internal-method-return-types https://php.watch/versions/8.1/internal-method-return-types).
- maverwa 5y agoYeah, the area between "backwards compatibility at all costs" and "progress" is full of potholes. I think PHP was to mach on the "backwards compat." site of that gradient, I think that some bc breaks are onavoidable when improving the language itself and its standard library. Sure, it would be nice to have something like rusts "editions" (and I am sure other languages share that concept to some degree) where we could have the runtime support all code that was valid before, but that comes with its own complexity. As someone who still owns their rent coding PHP, I really enjoy the development of the language from php 7 onwards. It certainly feels better in any way compared to the 5.x or even 4.x days. As long as we do not get another python 2 vs 3 disaster, I am happy.