What does HackerNews think of cdnjs?

🤖 CDN assets - The #1 free and open source CDN built to make life easier for developers.

This reminded me about https://github.com/cdnjs/cdnjs/ - every version of every popular JS library in one repository - one of the largest repositories on GitHub by size.
Cloudflare's cdnjs already exists, and allows people to contribute anything they like to it by making a pull request against https://github.com/cdnjs/cdnjs. Why would you choose to use this instead?
Another handy alternative to this site is http://cdnjs.com/ and their repo is located here: https://github.com/cdnjs/cdnjs.

This is typically what I use to offload hosted JS to a CDN although CloudFlare does a very good job. I had a problem early on with MaxCDN which powers http://www.bootstrapcdn.com/. While building http://gitignore.io, I had one pretty bad outage just as I was trying to promote the site so I first switched to cdn.js and then to CloudFlare and have been happy ever since.

It's half-way there. It could go a lot further. I'm really surprised there isn't a single (featureful) editor that follows the OSX/GNOME aesthetic of "convention over configuration; no preferences/options/modes if possible". Key-bindings are the same everywhere you go. Every command is available on every instance of the editor on everyone's machine, everywhere in the world. You never have to re-learn anything; you can just sit down and use all the features.

I would personally imagine something a bit like Sublime, but where all the "plugins" were actually just code contributed to the central codebase, and delivered by updates. (Specifically, I'm imagining it would work like Cloudflare's https://github.com/cdnjs/cdnjs for plugins.)

Given that the editor would then have "everything" in-the-box, it'd then probably have to have emacs-like modes, as well, to allow all the plugins' various key-bindings to live together.

Interesting results, but let's think about a few things before we all switch to Cloudflare CDNJS.

1) Time to first byte. In my experience the biggest lag is the connection, not actually downloading the file (for small js, images, etc...) I don't know how to test this.

2) Caching, by using google for common libraries like jQuery your chance of the end client already having a local cached copy are much greater.

3) Reliability. I know google has been recently killing off it's products, and even I tweeted how they could break the internet by shutting off their hosted library API, but it's probably not going to happen. Can you say the same about cloudflare?

I'm not saying I like one more than the other, but these are some things I would like to address before switching my and my clients sites over.

One thing I will give a +1 to Cloudflare is the ability to add js to the CDN via github. https://github.com/cdnjs/cdnjs

cdnjs.com (running on CloudFlare infrastructure) is an alternative to Google's CDN. We should have every major script, but if we're missing anything feel free to fork at https://github.com/cdnjs/cdnjs and we'll get it up asap.

Disclaimer: I'm one of the founders of cdnjs.