3 ms·
It's useful to consider not just download size, but also the time required to parse the extra code, and the extra memory used by the code that's parsed and load
by rpeden 10y ago
It's useful to consider not just download size, but also the time required to parse the extra code, and the extra memory used by the code that's parsed and loaded into memory, but not actually used.
Probably not a concern for desktop/laptop users, but there are plenty of mobile devices out there with relatively slow processors and 1GB of RAM or less.
- pspeter3 10y agoFrom Asana's page load numbers, it seems like most browsers now cache both the fetch and parse stages. The evaluation time is still a huge deal and I think the "Cost Of Small Modules" article that is referenced actually explains why quite well.
- franciscop 10y agoTotally, however that article was mainly about compression file size. The main problem when we get to optimization is that it highly depends on the browser and version. Parse time is still important, but I'd argue that it's related to both file size and processing power needed, but still less important than both of those.