The client side currently forces the user to download a lot of static files. A lot of these files were written by us and contain a small amount of code which needs to be run when the page loads.
I think we could improve this situation (without reducing the maintainability of the codebase) by merging a few files together and thus reducing the number of requests required by the client-side in order to render a page.
An alternative (which would be considerably better in terms of reducing page load complexity) would be to minify merge together a larger number of .js files and then minify them before sending them out - since this would be done as part of a build process we needn't worry about reducing the maintainability of the merged files. We could then require the user to download a smaller number of larger files.
McCrea
commented
10 years ago
The client side currently forces the user to download a lot of static files. A lot of these files were written by us and contain a small amount of code which needs to be run when the page loads. I think we could improve this situation (without reducing the maintainability of the codebase) by merging a few files together and thus reducing the number of requests required by the client-side in order to render a page.
An alternative (which would be considerably better in terms of reducing page load complexity) would be to minify merge together a larger number of .js files and then minify them before sending them out - since this would be done as part of a build process we needn't worry about reducing the maintainability of the merged files. We could then require the user to download a smaller number of larger files.