3 ms·
I personally still think that JS should still always be pre-processed. When you can spend longer up front optimizing the concatenation, minification, and compr
by andrewstuart2 12y ago
I personally still think that JS should still always be pre-processed.
When you can spend longer up front optimizing the concatenation, minification, and compression, you can amortize that additional cost across every request and still make important incremental gains.
A bit saved is a bit earned.
- Kudos 12y agoYou can and should still compress and do some amount of minification. Concatenation is debatable on sites with varied page types and JS needs. > A bit saved is a bit earned. So don't send bits the user probably won't need? :P
- Twirrim 12y ago> So don't send bits the user probably won't need? :P Surely good for both your bandwidth bills, and the end user experience. The less work your users have to do, the better, especially when it comes to mobile devices.
- swang 12y agoMost sites right now concatenate their _entire_ javascript blob rather than the "necessary" javascript blob for the current page. There are arguably other uses for minification and compression, but not needing to concatenate is going to save a lot of bandwidth since developers no longer have to consider whether or not they need to build another concatenated blob for specific pages.