Question

Can someone explain this? IE8

( function(){
    window.foo = function foo(){};
    console.log( window.foo === foo ); // false
}() );

Answer 1

Due to an IE bug, the named function expression creates a separate local foo variable with a separate copy of the function.

More info:

var f = function g(){};
f === g; // false

This is where things are getting interesting. Or rather — completely nuts. Here we are seeing the dangers of having to deal with two distinct objects — augmenting one of them obviously does not modify the other one; This could be quite troublesome if you decided to employ, say, caching mechanism and store something in a property of f, then tried accessing it as a property of g, thinking that it is the same object you’re working with.