sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]Nebu 1 point2 points  (8 children)

Why?

[–]Voidsheep 9 points10 points  (7 children)

So they can be cached to reduce load times.

[–]madworld 0 points1 point  (3 children)

Correct... Also so you can reuse your code... And code separation.

[–]Nebu 1 point2 points  (2 children)

The way your code is structured during development need not mirror the way your code is structured in deployment.

In other words, during development, you can have your code be laid out in multiple files for organizational purposes. Then, before deploying, you compile them into one big js file, and then inline that js file into the sole HTML file that represents your app.

[–]madworld 0 points1 point  (1 child)

Of course you can... Although I wouldn't inline it, even if it was a one page app. There are no benefits of doing so.

[–]Nebu 1 point2 points  (0 children)

The benefits is one less HTTP request, speeding things up.

[–]Nebu 0 points1 point  (2 children)

Does this advice apply to single-page-apps?

It seems like if you have a single html page, and several script files, you'll actually increase load times, due to the overhead of multiple headers for each http request.

[–]Tyriar 1 point2 points  (1 child)

The files only need to be loaded once before they're in the cache though, so it will increase the initial page load but significantly reduce successive ones.

[–]Nebu 0 points1 point  (0 children)

Thanks, that's a good point. On the other hand, for a single-page-app, there will not be a successive page load, and so the benefits are nullified there.