tag:blogger.com,1999:blog-14995055.post5405455238489960784..comments2009-08-12T08:10:03.995-04:00Comments on as simple as possible, but no simpler: Where should I define Javascript variables?Joel Webberhttps://profiles.google.com/111111598146968769323noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-14995055.post-50678509263735401902009-08-12T08:10:03.995-04:002009-08-12T08:10:03.995-04:00Thanks, Mark. I had forgotten about that mess. Thi...Thanks, Mark. I had forgotten about that mess. This is precisely the kind of thing that I think makes it so difficult to reason about Javascript and browser performance a priori. If you don't measure it, you're probably wrong :)joel.http://www.blogger.com/profile/18063235960332996797noreply@blogger.comtag:blogger.com,1999:blog-14995055.post-11008372664652098892009-08-11T18:59:17.593-04:002009-08-11T18:59:17.593-04:00> in any sane world, (window[name])
> would...> in any sane world, (window[name]) <br />> would be the same as (name), since <br />> they do precisely the same thing. <br />> But we're not in a sane world here, <br />> are we?<br /><br />Although these are equivalent according to the EcmaScript specs (both ES3 and ES5), it is not what most browsers do nor what the current html5 draft specifies. See<br /><br /><a href="https://mail.mozilla.org/pipermail/es-discuss/2009-July/009655.html" rel="nofollow">The global object in browsers</a>.MarkMhttp://www.blogger.com/profile/05982836560506229349noreply@blogger.com