60% true still. Most of the issues are in "wontfix" mode. I have seen this article so many times, and its still relevant, even a decade has passed. Make you wonder what the hell php devs are really doing?
Relevant in what way? Relevant as in they are factual or relevant to the day to day of a real PHP developer, because I can tell you the latter didn't hold up even when this was written.
> even a decade has passed
We got more optional typing and better error handling, and I'm still able to run the awful code I have written a decade ago.
Java is an almost 30 year old language and I can still do this:
String foo = null; System.out.println("hello" + foo.length());
> Make you wonder what the hell php devs are really doing?
Incrementally improving the language without breaking too much.
> 60% true still. Most of the issues are in "wontfix" mode.
Most of those are quirks that you can safely ignore, and "fixing" them would result in breaking a lot of the existing code, which is not worth it.
So is Python's yet the language is enjoying great success.
> All the builtin functions still have no namespaces, and no forced types.
And no PHP developer cares, because neither does C and yet it's doing just fine.
> PHP still coerces strings to ints and vice versa.
Which is great for beginners, because they don't need to worry about it, unlike me when I program in Rust and have to deal with 8+ number types.
> PHP still has serious bugs with its (only) collection, the frankenstein ARRAY.
So does JavaScript, yet it's not enough to stop the language.
> IIRC doing a array_filter is still broken on PHP8 for key val arrays.
There is some odd behavior if you try to do certain things in a functional style that is actually true.
> PHP still had no unicode in 2023, im not sure how the latest version fixed this or not. IIRC you had to use the weird mb_real functions to get anything closely functional, and it was a mess.
That can get annoying in some use cases, I have developed many international web apps in PHP, it rarely got in my way, but I do acknowledge that it's not great to not have Unicode by default, I suspect they are afraid to resolve this after seeing what happened with Python 3.