Use === instead; except for cryptography, where you want hash_equals().
> There's a lot of discipline/linting still required in PHP, whereas other languages won't even compile if you do something risky.
And/or just use scalar type declarations: https://3v4l.org/SJKe1
I've actually gone as far as rejecting commits that failed the linter and style checker, but that only works for code bases I have control over. It doesn't apply to the libs.
I now prefer languages where the entire ecosystem is passing strict compilation requirements.
That's not truthiness, that's implicit coercions.
Truthiness is specific to boolean contexts (if, while, explicit conversion to boolean).
What I really meant was that you have some $variable, and you test it in an if, while, etc. context. If the value is 0, it's false. But if you didn't realize you got a string from somewhere, it might be true. Unless it's an empty string? (I can't even remember.)
None of this changes the initial point, which is that writing "good" PHP requires enormous amounts of discipline, and that still doesn't address the security issues with PHP itself. I remember when the developer of Suhosin basically quit PHP and said he couldn't deal with the way its maintainers treated security issues.
I wouldn't take that criticism too personally. People also argue that C/C++ can't ever be secure due to the ease of programmer mistakes.