Shirmung Bielefeld: == ? === ??? ...#@^% | JSConf EU 

For 15 minutes it couldn't be more informative, thanks! For anyone who wants to dive deeper into this topic, look out for these: - the method toString is being implemented differently in the prototypes of the built-in function-constructors. That's the reason why dates, arrays, etc. are being converted differently into strings/numbers. The method toString is returning a primitive value (in the built-in objects it's returning a string usually but you can override that to return any primitive type) which is being converted into string/number based on the rules for converting primitive types into strings/numbers that were mentioned clearly in the video. You can easily check that: console.log(Object.prototype.toString === Array.prototype.toString) //false - if a Symbol.toPrimitive property (which value is a function) exists in the objects (including its prototype chain ofc), it's being converted into a string/number based on the rules that are defined in that function. That's the reason why dates are being converted differently into numbers compared to the other built-in objects. You can easily check what: console.log(Date.prototype[Symbol.toPrimitive]) //the property exists console.log(Array.prototype[Symbol.toPrimitive]) //the property doesn't exist. The instances are being converted based on the default rules that I already mentioned

Most detailed video on type coercions.....thank you.

Very well explained.

Extremely useful thanks :,-)

Great talk, Shirmung. I'm confused about these statements.. [] == false // empty list compared to false, returns true [] == true // empty list compared to true, returns false if([]) { console.log('True'); } else { console.log('False'); } // returns True :D How can list be both false and true ? :D, don't understand what's going on underneath the hood! Same case with Infinity!