Re:PHP in 2019
by GrumpyNl on Wednesday May 15, 2019 @07:55AM
(#19918500)
You can be burned by every program language if you dont know the in and outs. It all boils down to, pick the right language for the job and more important, know the language you choose.
[ Parent
| on HN ]
Re:PHP in 2019
by cljs-js-eval on Wednesday May 15, 2019 @08:35AM
(#19918750)
Seems like to know PHP, though, you need to know all the history that the author has picked up by following the PHP space since forever. Which mysql functions are appropriate, etc. If knowing the language means "being a working programmer in 2010 so that you could gain a working knowledge of the old APIs and some context for the new ones" I'm out. Keep PHP, I'll move to a different language where knowing historical baggage isn't a prerequisite.
There are languages which have great design from the start though (like Clojure).
PHP, javascript are not them.
Probably that's the reason why Clojure tends to be in top of the "developer happiness" polls.
.... and the bottom of "jobs available".
Re:PHP in 2019
by sethammons on Wednesday May 15, 2019 @08:38AM
(#19918767)
Languages have foot guns. Most however don't default to being loaded and already pointed at your foot.
I did know PHP. I was actually pretty good at and wrote non-trival software in it. Even then the relationship was pretty abusive. Even when I was writing bug free code the author of a library I was using wasn't or a co-worker wasn't.
It may in fact be that PHP has improved to the point that the relationship isn't abusive anymore. But I'll never go back to find out. PHP and me were done years ago.
Saying that all programming languages are equally good is about as true as saying that all sorting algorithms are equally fast.