* It's 2016 and PHP still doesn't have a module system, Python had one in '91, Perl had one in '94, Ruby had one in '95
Composer is widely adopted and has been the standard for years now. It's not baked into the language, it's a community driven effort that has been wildly successful.
* inequality operators still have no === equivalent
Still true. Pretty easy to deal with since there are functions for handling equality of all scalar types.
* sorting is still indeterministic when you have null values because NULL < -1, and NULL == 0
> * arrays are the only containers in the language and they simultaneously act as sets, lists, and associative arrays which fucks up almost all array functions because you don't know what they will do
Both of these things are true. Neither of these things regularly snag me in my development, but like many other dynamic languages, they do need to be carefully designed for. Unit testing, strongly typed scalar vars (new in PHP7), or using SPL object data structures instead of language primitive help here.
* PHP has had exceptions for almost 10 years now and a lot of functions still require you to use their specific error function to tell if it failed. So if you don't call say json_last_error, your code will SILENTLY return the wrong thing
I can't think of a function I regularly use besides json_encode that has this problem.
Much of that article was originally a disagreement with the approach PHP generally takes and is subjective in the first place. I'm not trying to sway people's opinion to actually use PHP, I'm just saying that despite the worts it is a capable language with an incredibly positive and productive community. It's no longer the dumpster fire it once was.
Comments
Composer is widely adopted and has been the standard for years now. It's not baked into the language, it's a community driven effort that has been wildly successful.
Still true. Pretty easy to deal with since there are functions for handling equality of all scalar types.
Both of these things are true. Neither of these things regularly snag me in my development, but like many other dynamic languages, they do need to be carefully designed for. Unit testing, strongly typed scalar vars (new in PHP7), or using SPL object data structures instead of language primitive help here.
* PHP has had exceptions for almost 10 years now and a lot of functions still require you to use their specific error function to tell if it failed. So if you don't call say json_last_error, your code will SILENTLY return the wrong thing
I can't think of a function I regularly use besides json_encode that has this problem.
Much of that article was originally a disagreement with the approach PHP generally takes and is subjective in the first place. I'm not trying to sway people's opinion to actually use PHP, I'm just saying that despite the worts it is a capable language with an incredibly positive and productive community. It's no longer the dumpster fire it once was.