2 ms·
> The permutations of different CDNs and asset versions meant the cache hit rate was low anyway. A CDN with DCs in a number of locations and appropriate DNS se
by dspillett 5y ago
> The permutations of different CDNs and asset versions meant the cache hit rate was low anyway.
A CDN with DCs in a number of locations and appropriate DNS setup at least has the advantage of local delivery which can have more than zero significance if you have an international audience and you really need low latency.
But if you are in that category then you probably won't (or shouldn't) be loading a bunch of stuff from a CDN or otherwise. And I wouldn't source script from a 3rd party anyway, I never saw the security tradeoff as worth it.
- ptx 5y ago> And I wouldn't source script from a 3rd party anyway, I never saw the security tradeoff as worth it. Doesn't subresource integrity [1], i.e. specifying the expected hash of the script, solve those security issues? Unless you need to support Internet Explorer, I suppose. [1] https://developer.mozilla.org/en-US/docs/Web/Security/Subresource_Integrity https://developer.mozilla.org/en-US/docs/Web/Security/Subres...
- dspillett 5y agoI want aware that had become so well supported. Something to remember for later. Though for personal projects I'll stick with self-hosting, and in DayJob we unfortunately still have to support IE11 to an extent (and beyond that some of our clients strictly whitelist everything and will reject a 3rd party they can't fully audit, ruling out CDNs for those at least, every with SRI).