Not sure I can agree on "understanding". Been using all sorts of languages for more than 10 years now and JS is quite inconsistent. I quite well understand it but dislike the approach. For me it's about taste. Ex. If I always get to convert the values for comparison why use == ever and why use dynamic typing? Using if where you don't care about type is fun but unpredictable as in what to put there? Always use .toString()? Always to number? To array? If I it depends on the use case why not always be strict about type since I know what shod be there?
It's a double edge sword. You win some you loose some
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.
Not sure I can agree on "understanding". Been using all sorts of languages for more than 10 years now and JS is quite inconsistent. I quite well understand it but dislike the approach. For me it's about taste. Ex. If I always get to convert the values for comparison why use == ever and why use dynamic typing? Using if where you don't care about type is fun but unpredictable as in what to put there? Always use .toString()? Always to number? To array? If I it depends on the use case why not always be strict about type since I know what shod be there?
It's a double edge sword. You win some you loose some