So php tries so hard to be Java. Well, just stick with Spring and get the job done professionally. Learning PHP these days is a waste of time.
PHP 8: Before and After
11–20 of 346 posts
Re: PHP 8: Before and After
#12So php tries so hard to be Java. Well, just stick with Spring and get the job done professionally. Learning PHP these days is a waste of time.
True but the php syntax is way too bad (like $ etc) in comparison to Java.
Re: PHP 8: Before and After
#13So php tries so hard to be Java. Well, just stick with Spring and get the job done professionally. Learning PHP these days is a waste of time.
Fishing?
Re: PHP 8: Before and After
#14Re: PHP 8: Before and After
#15Seriously, enough with PHP. Can we just let it die?
I worked with PHP 5.6 years ago and I hated it.
Recently I worked with PHP 7. Heard about all the work that's been done on it and I was kinda excited to try it. It's still so broken. It doesn't matter if they improve performance or add new cool features. PHP is broken in ways that can't be fixed without breaking compatibility. Fork it or put it out of its pain.
Re: PHP 8: Before and After
#16Earlier quoted context omitted.
Very soon: "A long-standing goal of the WordPress project is to be compatible with new versions of PHP on their release day. The next major version of PHP (version 8.0) is currently scheduled for release on November 26, 2020. WordPress Core contributors are working to ensure PHP 8.0 is supported in the next major version of WordPress (version 5.6), which is currently scheduled to be released on December 8, 2020." htt…
Possibly not what the author meant. Support for PHP 8 in WordPress will come soon after PHP 8 is released. But to upgrade WordPress to PHP 8, that is to rewrite its codebase to make use of PHP 8 features, probably will not happen anytime soon. WordPress still has a minimum PHP version requirement of 5.6, so...
Yeah, and just like in the case of Perl, PHP 5 isn't going away anytime soon; there's simply far too much legacy software running on top of it.
The WordPress ecosystem, on the other hand, will probably make the switch much sooner.
Re: PHP 8: Before and After
#17I am not a developer, but by far most of the code I had to write in the past 5-6 years was in PHP. I see it going in a direction where it is no longer PHP, but trying to be something else it will never be (Java? C#?), so I may continue using it as long as it is backward compatible and that's it: good bye PHP, I am the same but you are not. I am not resistant to change, just the reasons I picked PHP versus something else are going away.
Re: PHP 8: Before and After
#18It's becoming kind of an Enterprise language [1]. Don't get me wrong I think PHP is getting cooler, hopefully everybody catches up and the fact that You can have a shared hosting for pennies run Your PHP code really puts it at an advantage compared to others. [1]: https://github.com/joaomilho/Enterprise
Lately I see myself abusing (???) types more often than ever. Before, I'd feel comfortable returning an array of structured data from a function. Now, I'm creating Value Objects to ensure my data is both valid and correctly used elsewhere. Kinda feels nice to get intellisense working too and knowing that the things that I'm trying to do with that VO are valid
Re: PHP 8: Before and After
#19Seriously, enough with PHP. Can we just let it die? I worked with PHP 5.6 years ago and I hated it. Recently I worked with PHP 7. Heard about all the work that's been done on it and I was kinda excited to try it. It's still so broken. It doesn't matter if they improve performance or add new cool features. PHP is broken in ways that can't be fixed without breaking compatibility. Fork it or put it out of its pain.
Live and let live. There is enough space in this Universe for you and PHP to coexist without interacting, if you don't like it then ignore it.