But I wanted to point out two things to consider.

First, every time you add a domready event to the window, you’re not adding another event to the window in some way that is an expense. Really you’re doing exactly what you’ve shown above – adding a function to an array of functions that need to be executed when the dom is ready. Calling addEvent on window just pushes the event into an array of methods to call when the event fires. There’s no real expense to adding the event, and there’s no saving of cycles by using your array pattern here.

The second thing to consider is that the domready event keeps track of whether or not the dom has *already* loaded. Meaning that if you add a domready event and domready has already fired, your method will be executed immediately. This is really useful for code that has to occur after domready but you’re not sure when it’s being run (I use this a lot in plugins I release).

I agree that keeping all your “initialize” code in one place is really useful (though it’s not always practical). Using your array method here might feel more tidy than a bunch of domready statements, but it amounts to the same thing – a collection of methods that all run when the document is ready for them.