Why you guys talking about minuses of jQuery? Donate some bucks to jQuery creators instead.
JQuery SSL Certificates Expire
31–40 of 44 posts
Re: JQuery SSL Certificates Expire
#32Wow, how can a prominent internet library that advises its users to use this server make such an avoidable rookie mistake...
Well, because chances are they gave the job of renewing the certificates to the rookie, and he may not have known how to do it, or raised the issue multiple times and nobody knew the implications of it. I know the last place I worked at, I mentioned that the certificates were expiring, and I needed to pay to renew them, yet they didn't seem to care until our customers couldn't connect anymore.
Re: JQuery SSL Certificates Expire
#33Earlier quoted context omitted.
Wouldn't this be solved by hosting it on your own site?
I assume that will work,but it will introduce two problems. 1. Keep a local copy means you will be the one paying for the bandwidth to serve it. 2. You will have to manually update your local copy everytime upstream makes improvements. Having things locally increases reliability but it carries its own costs.
You will have to manually update your local copy everytime upstream makes improvements.
Isn't this true of every library, framework, language, kernel, etc, that drives websites?
Re: JQuery SSL Certificates Expire
#34Any "big" website is broken because of this?
Big websites would host jQuery themselves typically on their own CDN.
Re: JQuery SSL Certificates Expire
#35Earlier quoted context omitted.
Wouldn't this be solved by hosting it on your own site?
I assume that will work,but it will introduce two problems. 1. Keep a local copy means you will be the one paying for the bandwidth to serve it. 2. You will have to manually update your local copy everytime upstream makes improvements. Having things locally increases reliability but it carries its own costs.
Keep a local copy means you will be the one paying for the bandwidth to serve it.
This should never be a consideration. It's not really stealing bandwidth, since all are welcome to download, but the idea that an asset my site (which presumably makes money) needs should be paid for by someone else really is in the same ballpark ethically.
Re: JQuery SSL Certificates Expire
#36Why not use Google's CDN? https://ajax.googleapis.com/ajax/libs/jquery/1.10.2/jquery.m...
I am some kind of weird mutant because I consider having external javascript on my website to be an embarrassment for anything bigger than a hobby project -- but 99% of the universe behaves otherwise.
Re: JQuery SSL Certificates Expire
#37Earlier quoted context omitted.
I assume that will work,but it will introduce two problems. 1. Keep a local copy means you will be the one paying for the bandwidth to serve it. 2. You will have to manually update your local copy everytime upstream makes improvements. Having things locally increases reliability but it carries its own costs.
How is getting upstream "improvements" without having a chance to test them a good thing?
"Users want and demand a rich computing experience."[1]
Re: JQuery SSL Certificates Expire
#38Why not use Google's CDN? https://ajax.googleapis.com/ajax/libs/jquery/1.10.2/jquery.m...
I am some kind of weird mutant because I consider having external javascript on my website to be an embarrassment for anything bigger than a hobby project -- but 99% of the universe behaves otherwise.
That's because the other 99% understands how browser caching works. If you use JQuery.com, Google, or Microsoft's CDNs then MOST of the time users won't have to download a JQuery/Boostrap/etc library as the browser would already have an unexpired cache of it.
For example, the OP's link's cache will expire (theoretically) in the year 2079. So if a user visited ANY page that utilises JQuery v1.10.2 they already have it. That is a HUGE win. It is an even huger win for mobile (e.g. for small sites you could cut your network traffic in half, which in turn increases loading speed).
It is also trivial to set it up so the page tries the CDN first and if that fails then grab a local copy e.g.
window.jQuery || document.write('\x3C/script>')
Re: JQuery SSL Certificates Expire
#39Earlier quoted context omitted.
I am some kind of weird mutant because I consider having external javascript on my website to be an embarrassment for anything bigger than a hobby project -- but 99% of the universe behaves otherwise.
That's because the other 99% understands how browser caching works. If you use JQuery.com, Google, or Microsoft's CDNs then MOST of the time users won't have to download a JQuery/Boostrap/etc library as the browser would already have an unexpired cache of it. For example, the OP's link's cache will expire (theoretically) in the year 2079. So if a user visited ANY page that utilises JQuery v1.10.2 they already have it…
Would just using another CDN be just as safe?
Re: JQuery SSL Certificates Expire
#40Earlier quoted context omitted.
That's because the other 99% understands how browser caching works. If you use JQuery.com, Google, or Microsoft's CDNs then MOST of the time users won't have to download a JQuery/Boostrap/etc library as the browser would already have an unexpired cache of it. For example, the OP's link's cache will expire (theoretically) in the year 2079. So if a user visited ANY page that utilises JQuery v1.10.2 they already have it…
Would just using another CDN be just as safe?
Some users block the big CDNs for privacy reasons, so local is a safe fallback.