3 ms·
That's really useful. I've wanted this exact thing a couple of times. They say not to use this CDN for anything production related, but I personally think you
by AdrianRossouw 13y ago
That's really useful. I've wanted this exact thing a couple of times.
They say not to use this CDN for anything production related, but I personally think you shouldn't be using any public JS CDN for anything that matters.
reasoning here :
http://daemon.co.za/2014/03/from-trenches-js-cdn-point-of-failure/ http://daemon.co.za/2014/03/from-trenches-js-cdn-point-of-fa...
- timdorr 13y agoIf you check the bottom of the page, you'll see they've set up a production-ready CDN via MaxCDN: http://rawgit.com/#cdn http://rawgit.com/#cdn
- AdrianRossouw 13y agoYes, I recommend not using using any public cdn. That includes cdnjs, google hosted libraries, maxcdn. anything. I think that you will inevitably end up needing to host code that uses the external dependencies, and you should host your libraries from the same 'place' that your code ends up on. It's about data locality and reducing moving parts.
- madeofpalk 13y agoAlso, using an external CDN will end to more downtime. You'll never benefit from having your CDN up if your own servers are down.
- AdrianRossouw 13y agoThinking about it now, if you could host your own code via the CDN (which this implies), that's perfectly fine with me. It's late =P I'm leaving my sibling comment untouched since my point still stands.