1. Other languages also do not have this distinction (Python for example AFAIK),
2. It's relatively useless. I get the value of it in JavaScript which has a lot of asynchronous code and frontend where the behavior may indeed be very different between null and undefined, but in a server-side application I don't think the nuance is necessary at runtime, and potential programming mistakes involving that can be caught by a linter.
[1] https://stackoverflow.com/questions/6905491/how-to-tell-whet...
This is a discussion for us tech folks. When it comes to business. Customers don't give a rat's ass about this as long as the product provides them with value.
If you're flooded with customers and the tech stack is a pain in the ass, perhaps it would be a good time to start considering this, but until you have this problem, the technical aspects are just wasting investor money and / or engineering time.
For most companies, issues like `undefined | null` bugs can be resolved with just a few code adjustments, resulting in only minor inconvenience for customers. As long as problems are addressed and the product provides value, customers will continue to support it.
There are CEOs and CTOs that feel differently. I wish them luck.
At the language level PHP has about the same problems as JS.
Thankfully it looks uglier so people get an early warning before using it for everything.
So?
Don't similar footguns appear in Python and JS? Why single out PHP for footguns when the other languages are no better?
While I'm not a PHP programmer, I have used most programming languages, and PHP doesn't seem any worse than the competitors.