// wherever we are
var global = function(){return this}();
// while window, could be simply a variable
// assigned somewhere else in this scope
I have already talked about this, and I am still against some ES5 "feature" which aim is probably the one to make JavaScript as fast as possible, regardless all code that will break if "use strict" is present in the generic scope.
Another non-sense is to allow a this in a context where there is no this. Rather than an error, ES5 will point refer this to undefined.
Are you kidding me? this is a special keywords related to the context and you are telling me a context is undefined? so I guess open(), as example, should throw an error there, since window cannot be implicit in an undefined context, isn't it? ... anyway, fortunately the whole problem could be quickly solved in this way:
// ES5 problem
(function(){
"use strict";
this === undefined; // true ... LOL!!!
})();
// WebReflection QAD solution
(function(){
"use strict";
this === window; // true ... yeah baby!
}).call(this);
This simple modification could avoid lots of headaches plus could avoid scope resolution for every window variable.
It's probably quite obvious but I can already imagine lots of people changing the whole function body rather than add a call at the end :D
The trick to retrieve the global context won't work in any case for nested functions, unless we are not sure that this points to window, but being the trick goal the one to make window resolution quick and safe, there is not window,self,top, whatever check that could solve the problem (unless [].sort() will be still buggy ...)
As summary, the day JavaScript will be that fast thanks to removed dynamic and run-time features, it won't be JavaScript anymore but another language a la ActionScript 2 when ActionScript 1 was enough, and the problem was the player rather than the language, which indeed has been replaced by ActionScript 3 even if the problem is still the player and not the language, since it can be compilable into old versions.
