Live data from Hacker News

PHP in 2022

stitcher.io

1–10 of 318 posts

Re: PHP in 2022

#8
I was a php developer for some time two years ago, before switching to go.

I was mainly solving high performance parallel processing and distributed problems.

There are things like ReactPHP which are an awesome achievement, but still every lib you use needs to be developed for ReactPHP.

After learning about go and goroutines I only find it painful to solve these problems in PHP, even using ReactPHP.

Re: PHP in 2022

#9
Is it just me or PHP's evolution is a bit "too little, too late" for an almost 30-years old language?

PHP is not a likable language but it's probably not going away any time soon. Its concept of "one endpoint is one script" is one of its biggest killer features that no other language has been able to deploy in such an accessible manner. Well, Perl and old-style CGI aside, of course.

That, and also the fact that it may be pretty much the only dynamic language in use today with ARC and not a GC. Funny how PHP devs are often unaware of this.

Anyway I wish the language at least evolved faster and we wouldn't wait for 8.0 to have global `const` definitions instead of the archaic `define()` for example.

Re: PHP in 2022

#10
post #8

I was a php developer for some time two years ago, before switching to go. I was mainly solving high performance parallel processing and distributed problems. There are things like ReactPHP which are an awesome achievement, but still every lib you use needs to be developed for ReactPHP. After learning about go and goroutines I only find it painful to solve these problems in PHP, even using ReactPHP.

So you switched from a language X not designed to do Q to a language Y designed to do Q, presumably because language Y didn't exist when you started doing Q. I imagine that happens all the time, but seldom is it a fault of X. But what I find puzzling is why PHP, of all things, was your choice for these kinds of problems before Go appeared.
Post reply on HN