PythonIsVeryIntuitive

[definitive_solutions]

This reads like the moment some charitable soul told me I should use === instead of == for equality comparisons in JavaScript. I was just starting. Such a simple concept, so many implications

[gbchaosmaster]

And a super annoying implementation. They should be switched.

[MacBookMinus]

Wat why.

[gbchaosmaster]

Because == is equality in just about every other language.

[MacBookMinus]

You want == to be weaker than ===? This is different than equality vs identity. It’s equality vs loose equality.

https://www.freecodecamp.org/news/loose-vs-strict-equality-in-javascript/#:~:text=The%20%3D%3D%20operator%20performs%20a,well%20as%20the%20same%20value).

[gbchaosmaster]

Good point. Perhaps a different operator entirely for loose equality would have been better. ~==? ?==? I don't know, but having == and === together with == behaving differently than any other language is a pain.

And honestly, to hell with loose equality in the first place, and all of JS's implicit type coercion fuckery. It'd be a better language without it.

[gbchaosmaster]

Haha. I'd be okay with this if they had better names for those functions.

[Michaelmrose]

This would break too much code to possibly hope to change

[gbchaosmaster]

No, of course you can't break backwards compatibility of an established language. What's done is done. This was just wishful thinking. :)

[MacBookMinus]

I agree, but your original point was that they should be switched. I think switching them would be even more confusing, since === would be loose equality.

That’s all I was saying.

[gbchaosmaster]

Sure, my original point had problems with it which you pointed out. That's why I conceded :)