Are there any repercussions to storing globals like this?

Question

So I know polluting the global namespace referencing the window is a bad thing, especially if you have multiple 3rd party references. So this would be not desirable:

window.someObject = someObject;

That will reference it everywhere. What if I instead use it like this?

var MyApplication = window.MyApplication;
MyApplication.someObject = someObject;

Of course using this approach requires referencing MyApplication = window.MyApplication at the top of each module that needs access to this created namespace. So back to my question. Is this an acceptable approach to giving global access without polluting the window global namespace?

Answer 1

If you want global access, you need to have a global of some sort. This is the common way of doing it.

An example from the jQuery source code:

_jQuery = window.jQuery,
_$ = window.$,

I believe all of the big frameworks do it this way. I'd consider it perfectly acceptable to pollute the global namespace with one container variable.