Except strict equality, that’s a JavaScript only problem. Imagine thinking "0" should be falsy in comparison due to string literal evaluation, but truthy with logical not applied based on non-empty string. Thus !"0"=="0" is true. They couldn’t just throw away == and start over nooooo let’s add === . Utter madness
High level folks complain it takes too long to code in and is hard to understand the borrow checker. Low level folks complain it takes too long to code in and is hard to understand the borrow checker. Honestly though the borrow checker is a great compromise to idiot proof memory leak prevention, and the C folks can just throw in unsafe when they want start slinging pointers and manual heap management. The macro system alone is so good I don’t think it’s fair to appraise the language until you’ve written a dozen macros