3 ms·
It's not just the download size and CDN utility in caching JS on the client side for reuse -- on older machines or devices with less than shiny new execute powe
by pauljonas 13y ago
It's not just the download size and CDN utility in caching JS on the client side for reuse -- on older machines or devices with less than shiny new execute power, all that code make for a sluggish UX experience. Maybe not in seconds, but even a hundred milliseconds can make for a huge difference, even if it's not readily apparent.
- jon_kuperman 13y agoIf the code is already cached on the device, which I'm assuming it is in most cases. What is it that is slowing down the UX experience?
- userbinator 13y agoCached doesn't mean free. Every byte of JS still has to get parsed even if it won't ever be used. I really like how this demoscene-like mentality of being efficient with our computing power by only applying the minimal, needed complexity has started to get a more mainstream following. The traditional approach of piling on more complexity in the form of abstractions and other things is simply not sustainable. "The fastest way to do something is to not do it at all."