And just loop over the nodes. Maybe add prefix in each comments to id them..

eg.

@V1 ooo… I like that thought! But how would you divide that into “modules” of executable content?

But consider this… move a bunch of commented out, minified script to the bottom of the page? You could add an ID to each script block, grab the content, remove the comment and re-inject it into the block… that would incorporate a majority of this feedback, no?

I have a feeling we’re discussing milliseconds of time, though. It’s a great concept.

But one thing i’m wondering about on this technique is why they put the modules inside tags instead of plain HTML comments.

You can read the DOM HTML comments nodes, and inject eval its contents. This will probably speed up the page even more as the browser does not need to load a script tag at all.

(At least if my interpretations are correct on this )

@Marcus: It would be easier to create script DOM elements in the main page than via an iframe.

@Clint: Hi, Clint! Setting the innerHTML will work and is probably slightly faster than eval.

Worth testing out, but I’m thinking if it’s more than a hundred microseconds faster, it’s because the browser’s doing something dumb.

I wonder if it would be faster if you simply set the innerHTML of the script tag to the comment-stripped string, rather than eval? Doesn’t the code get executed in this manner with XHR injection?

using an iframe on the same domain which in turn loads a js file from a foreign domain (in which the code is in a comment block) would probably have the same performance benefit as loading the js directly into an iframe. It would also work for any website despite domain setup.

What do you think?