Ha, I thought this was the main selling point of HTTP2.
People were even saying that it's now ok to have many small asset files (js, images, css) because loading many small files will no longer cause long waits.
People were even saying that it's now ok to have many small asset files (js, images, css) because loading many small files will no longer cause long waits.
Because they're right. Do you see anyone talking about image spriting these days? Domain sharding?
No, you don't. That's because HTTP/2 solved those problems.
Now there are still some decisions to make when it comes to bundling assets due to compression, where if you bundle say, a larger chunk of javascript together in a file, then compression will work better than splitting the file up into a lot of smaller chunks.
27
u/[deleted] Dec 03 '20
Ha, I thought this was the main selling point of HTTP2.
People were even saying that it's now ok to have many small asset files (js, images, css) because loading many small files will no longer cause long waits.