> for the next unityped trap Many languages are unityped and carry the same problems, yet they are hyped rather than bashed (e.g. Python, Ruby). > If you know

> for the next unityped trap Many languages are unityped and carry the same problems, yet they are hyped rather than bashed (e.g. Python, Ruby). > If you know why you shouldn't use `==`, you know enough so that even if you don't go for `===`, using `==` safely is the least of your problems. You have some weird false dichotomy going on. I'm personally in the state "I remember why == is bad (type coercion ...)" but I don't remember all the details to be able to use == correctly. I bet many people are in a similar situation.