Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author Milan Dini?

    (@dimadin)

    First reason why I choose jsDelivr is that everything we need (core, plugins, themes files) is automatically there, no need to manually do something, they simply proxy repositories we need. With cdnjs, there are only manually selected JavaScript libraries, it would work with some popular libraries (like jQuery, for example), but not with all other JavaScript/CSS files that can be used by WordPress site, especially those coming from plugins and themes. So there are no really options right now what CDN to use.

    Second reason is that it has multi CDN infrastructure (including using Cloudflare, that cdnjs uses), it doesn’t rely on single CDN service, and it has better coverage in some parts of the world (such as China).

    I actually tried cdnjs in the past, I wrote about all of this in my blog post.

    If things change in the future, I might reconsider my options, but I doubt that it will be in this plugin, I do not want to add settings/options, maybe release a new plugin.

    Thread Starter Will Stocks

    (@willstockstech)

    Just read through that post – all makes sense!

    Hopefully jsDelivr usage starts to increase, so there’s a higher chance of users already having stuff cached ??

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Other CDN’s in the future?’ is closed to new replies.