Fair enough. I didn't mean insane in the sense of completely without reason, just in the sense that it was badly thought out.
The thing is that nulls are now baked into JS at a few levels, so in our own code we can avoid them, but they pop up throughout the various JS apis, eg
That's what I mean by the loose "insane" comment. It was a mistake that was bad enough that as JS devs we're now best off to generally avoid the fundamental null value in JS.
I totally agree with you about TS, which corrects many of these issues, and how in JS we're best to use undefined whereever possible.
We're a place where coders share, stay up-to-date and grow their careers.
We strive for transparency and don't collect excess data.