187
Google Chrome coders really, truly, absolutely ready to cull third-party cookies from 2024
(www.theregister.com)
This is a most excellent place for technology news and articles.
Running a CDN on your domain effectively defeats the purpose of CDN.
No. Things being on your domain doesn't mean that traffic hits your servers.
It doesn't, but it defeats the purpose of CDN, because your users still hit your domain instead of CDN one and cannot leverage the benefits of distributed caching. Browser cache is bound to a URL, you change one letter and it is invalidated.
Why would the URL change?
It won't share js libraries and fonts and whatnot cross-site but compared to a single image that should be negligible. At least if you don't pull in gazillions of superfluous dependencies and don't even run dead code elimination over them. And anyway that's more bandwith usage between user and CDN, not user and you.
Also I already said that it's insanity. But it would work.
Because you're not using a CDN URL everyone else is.
Savings are massive for the user. If you don't care about your users, please stop doing anything development related.
You know what's faster than a CDN? Vanilla js.
And how often do I have to repeat that it's insanity? It's just that user network traffic doesn't even come close to the top of reasons why it's a bad idea.
Insanity is what you have in your head.
I wasn't the one advocating to outlaw cross-site everything. I only said that it could be made to work... not well, but still. Also that it's a bad idea. Do you disagree with that?
But yes I'm also insane how could you tell.