It's not a sign of maturity or seniority to laugh at other peoples code. We have all been there, whatever the circumstance, non-optimal code is written in the real world every day.
I don't even see the problem here, in loosely typed languages, I will always use the === operator especially if other people work on the same codebase. Yes, in an optimal world you would not need this, but that does not reflect reality and in this case actually helps preventing hard to track bugs if you make the condition strict.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
It's not a sign of maturity or seniority to laugh at other peoples code. We have all been there, whatever the circumstance, non-optimal code is written in the real world every day.
I don't even see the problem here, in loosely typed languages, I will always use the === operator especially if other people work on the same codebase. Yes, in an optimal world you would not need this, but that does not reflect reality and in this case actually helps preventing hard to track bugs if you make the condition strict.