Closed markhealey closed 10 years ago
Hey guys, I am the owner of jsDelivr so naturally I vote for jsDelivr :) But I would like to list a few interesting features that jsDelivr has:
Let me know if you have any questions or feedback.
Correct me if I'm wrong, but hasn't cdnjs been pretty slow at incorporating our releases? so I vote jsdelivr.
@brianbaker It wasn't that they were that slow, we were inadvertently omitting the "author" qualifier in the pull requests. Still it isn't happening within a day or two.
Hey guys,
speed of merging has definitely become a problem as we've grown. Our first step to tackle this problem has been to build an auto-pull-from-npm tool that runs every few hours.
https://github.com/cdnjs/cdnjs#enabling-npm-auto-update
If you don't get around to editing the package.json I will jump on it over the next few days.
cdnjs has been fast at deploying new versions since adding the [author]
flag in the title of the pull request. Closing this out as I haven't seen enough reasons to switch.
And today CDNJs is faster than JSDelivr http://www.cdnperf.com/
It was suggested (via email) F2 javascript files get moved to jsdelivr from cdnjs for better overall support in addition to a bigger network footprint and higher uptime. In case you aren't aware, F2 introduced CDN support in September 2013.
I'd like to open the poll for voting on the issue. Looking at this uptime chart jsdelivr outperforms cdnjs.
Comment with
cdnjs
orjsdelivr
to cast your vote.Thanks.