4 ms·
>where little to nobody gives a shit about page load time. If it has an end user that is not yourself, I can guarantee you they do care - even if it's not a co
by djm_ 9y ago
>where little to nobody gives a shit about page load time.
If it has an end user that is not yourself, I can guarantee you they do care - even if it's not a conscious realisation.
- mattmanser 9y agoDepends on your target audience. If it's 10 internal admin users on desktops, the only time they're going to have to redownload the bundled js is when there's a change. And if you're sensible you'll have multiple bundles, one of which will be a bundle of rarely updated external libraries, including that editor. So once every couple of months they have to wait an extra second or two for a page to load. Some of the internal apps I've written for clients have a core bundle that almost never changes and then a js file almost per page (which each append a hash of their contents to the URL to ensure efficient cache busting, managed with an in memory cache of the hashes).