303 karma · joined January 18, 2011
The CDN portion is completely independent of the website. The website is really just an index of the files on the CDN.
http://blog.cloudflare.com/cdnjs-community-moderated-javascr... https://www.cloudflare.com/apps/cdnjs
As for Cloudflare's speed, you can see cdnjs's average ping time as measured by pingdom here: http://stats.pingdom.com/4jg86a2wqei0/362854
As for the security of our system, all javascript files are verified against official sources before going on the cdn. Additionally, we have many library maintainers submitting updates to their own libraries.
Beyond that the only question remaining is our personal integrity. Like any relationship with a third party, you're going to have to decide whether trusting us is an acceptable level of risk. If past performance is any indication of integrity, we have had no security incidents since we began in January 2011.
e.g. My car has 200hp and can do a quarter mile in 20 seconds. If I then increase my car to 400hp (a 100% increase), let's pretend I can now do a quarter mile in 10 seconds.
Thus, a 100% increase in performance drops cuts my quarter mile (or in this case processing) time in half.
I can't thank you enough! Props to helping people discover Essential Mixes.
The other thing you're not considering is that Facebook displays more than just text. If you're displaying images inline as well as text, it's going to be more compact if you interpolate each post in a zig-zag fashion rather than making posts vertically serial.
The example you provided doesn't really illustrate why timeline is bad for a website because it's an example provided in a completely different context.
tl;dr Website design is not command line interface design.
Disclaimer: I'm one of the founders of cdnjs.
From http://www.asp.net/ajaxlibrary/cdn.ashx#ajaxmicrosoftcom_ren...:
The CDN used to use the microsoft.com domain name and has been changed to use the aspnetcdn.com domain name. This change was made to increase performance because when a browser referenced the microsoft.com domain it would send any cookies from that domain across the wire with each request. By renaming to a domain name other than microsoft.com performance can be increased by as much to 25%. Note ajax.microsoft.com will continue to function but ajax.aspnetcdn.com is recommended.
The program to which you refer (http://stronglifts.com/stronglifts-5x5-beginner-strength-tra...) seems to be a slightly different spin on Mark Ripptoe's legendary Starting Strength program (http://startingstrength.wikia.com/wiki/The_Starting_Strength...).
If you are serious about improving your strength and health in general, buy Mark's book (http://www.amazon.com/Starting-Strength-2nd-Mark-Rippetoe/dp...). It is probably the best $30 investment I have ever made.
NB: I am in no way affiliated with Mark Rippetoe. I simply have incredible respect for the man.
We're looking into jumping ship to Rackspace once they complete their move to Akamai for Cloud Files (anticipated to be finished by the end of Q1 this year). It seems like they will support the Accept-Encoding header: http://news.ycombinator.com/item?id=2097491
We did stuff up the launch of this service. We should have thoroughly vetted DNS propagation before we launched. We plan to learn from this, and will ensure anything we do in the future has much more rigorous testing.
Please accept our humble apologies.
We're working on resolving current issues as we speak.
Given the how cheap CloudFront works out to be for files of that size, we can support quite a lot of growth, even if we have to incur the expense personally.
We do plan to monetize it at some stage. Some ideas are premium accounts that mash all of your resources together and host them for you.
-----------
We might have to put that one down to initial technical difficulties.
Not sure why you are getting access denied for that particular resource. May have to invalidate that object from CloudFront cache locations.
EDIT: We are using Amazon CloudFront to host the scripts.
For some reason, the main site is taking ages to propagate to some DNS servers.
You're probably covered by one of the servers with an (x) here: http://www.whatsmydns.net/#A/cdnjs.com
This doesn't actually affect the CDN side, which hosts the scripts.
EDIT:
For example:
http://ajax.cdnjs.com/ajax/libs/backbone.js/0.3.3/backbone-m...
http://ajax.cdnjs.com/ajax/libs/underscore.js/1.1.4/undersco...
http://ajax.cdnjs.com/ajax/libs/modernizr/1.6/modernizr-1.6....