Cdnjs - the missing cdn • Hacker News Board

Re: Cdnjs - the missing cdn

#61

Post by jsdalton » Tue, Aug 21, 2012, 4:20 PM UTC

What's the policy on previous versions of libraries?

I noticed, for example, that only the latest version (3.1) of the jQuery plugin Nivo Slider is available. The last versions (Given that the previous version was released in May 2012 that's an insanely fast deprecation policy for a CDN.

I have to guess that either I've stumbled upon a bug or minor oversight in this case, because I can't see how removing old versions that quickly would be at all a workable solution for 99% of use cases...

Re: Cdnjs - the missing cdn

#62

Post by jsdalton » Tue, Aug 21, 2012, 4:22 PM UTC

mpd wrote: post #60

What about old versions? Taking the jQuery url, and changing it to the version previous to the newest release (1.7.2), 404s on me. This is a showstopper. http://cdnjs.cloudflare.com/ajax/libs/jquery/1.8.0/jquery-1.... - ok http://cdnjs.cloudflare.com/ajax/libs/jquery/1.7.2/jquery-1.... - 404

Ha, you and I noticed the same thing just moments apart. Hopefully someone will reply on this thread to our question, because I can't imagine having to upgrade all of my projects immediately whenever a new version of any library was released.

EDIT: Looks like the URL pattern just changed slightly for jQuery. 2.72 is still around:

http://cdnjs.cloudflare.com/ajax/libs/jquery/1.7.2/jquery.mi...

Looks like they host back to 1.6.1, probably when the library was added to the project:

https://github.com/cdnjs/cdnjs/tree/master/ajax/libs/jquery

Re: Cdnjs - the missing cdn

#63

Post by jonny_eh » Tue, Aug 21, 2012, 4:42 PM UTC

jsdalton wrote: post #61

What's the policy on previous versions of libraries? I noticed, for example, that only the latest version (3.1) of the jQuery plugin Nivo Slider is available. The last versions ( Given that the previous version was released in May 2012 that's an insanely fast deprecation policy for a CDN. I have to guess that either I've stumbled upon a bug or minor oversight in this case, because I can't see how removing old version…

Maybe they'll only support version that were released from the date that library was added to the CDN. In other words, hopefully once a library+version are added to the CDN, it's supported for a long long time.

Re: Cdnjs - the missing cdn

#64

Post by jonny_eh » Tue, Aug 21, 2012, 4:46 PM UTC

mkoryak wrote: post #21

and here is the other 'missing' cdn that does the same thing and has been around longer: http://cachedcommons.org/ :)

No SSL support? I'll stick with cdnjs.com

Re: Cdnjs - the missing cdn

#65

Post by jsdalton » Tue, Aug 21, 2012, 5:12 PM UTC

jonny_eh wrote: post #63

jsdalton wrote: post #61

What's the policy on previous versions of libraries? I noticed, for example, that only the latest version (3.1) of the jQuery plugin Nivo Slider is available. The last versions ( Given that the previous version was released in May 2012 that's an insanely fast deprecation policy for a CDN. I have to guess that either I've stumbled upon a bug or minor oversight in this case, because I can't see how removing old version…

Maybe they'll only support version that were released from the date that library was added to the CDN. In other words, hopefully once a library+version are added to the CDN, it's supported for a long long time.

Yes, I think you are correct.

Digging deeper, I see that libraries are added via pull request and that the Nivo Slider library was added 11 days ago. Other libraries that have been there longer (such as jQuery) continue to have old versions.

Re: Cdnjs - the missing cdn

#66

Post by MatthewPhillips » Tue, Aug 21, 2012, 5:46 PM UTC

sp332 wrote: post #56

MatthewPhillips wrote: post #54

Earlier quoted context omitted.

Subscriptions would not support the development costs of that.

Ars Technica seems to be doing fine with it. http://arstechnica.com/subscriptions/#features

Doesn't say anything about being JavaScript free. Ads are not the only use of JS you know.

Re: Cdnjs - the missing cdn

#67

Post by moe » Tue, Aug 21, 2012, 5:55 PM UTC

Hint: If you want to brag about your uptime ("100%") then you should monitor that with a HTTP-request and not an ICMP Ping.

The latter is rather deceptive because it's not actually testing service availability.

Re: Cdnjs - the missing cdn

#68

Post by sabat » Tue, Aug 21, 2012, 6:03 PM UTC

debacle wrote: post #41

Needs more wu.js http://fitzgen.github.com/wu.js/

From what I've gathered, you can fork cdnjs, add it, and do a pull request.

Re: Cdnjs - the missing cdn

#69

Post by px1999 » Tue, Aug 21, 2012, 6:26 PM UTC

Looks really useful at serving the stuff that you can't find anywhere else (and for whatever reason don't want to host yourself), but IMO it really needs a TOS / license - I'm guessing that I can use it on personal sites, but can I use it on commercial sites, can I use it on SaaS sites, or sell sites that use it, etc etc?

Re: Cdnjs - the missing cdn

#70

Post by dalore » Tue, Aug 21, 2012, 6:42 PM UTC

mdlthree wrote: post #39

What do providers get for access to these type of files? Can they capitalize on the information gathered from file requests? Adding to their knowledge of traffic patterns etc...

Primed caches? Faster access for their clients who use the cdn?