I didn't want to add to the volume of responses until you had a chance to read what was already said. Here's my take -
- Google is very reliable with 99% or better uptime.
- If you use Google, chances are that many of your first time users will already have the Google script in cache, saving time loading your pages.
- You can easily download a Google hosted script for your own use. Simply make a link to it on an .htm, or .html page, or any page you can view in your browser as HTML, example -
download.htm (call it anything.htm):
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
Right click and "Save As":
is the version you want. Notice that I have only 1.8 there. That will get you the lateset in the 1.8 series (1.8.2). Similarly you can use 1.6 for the latest in the 1.6 series (1.6.4), or just 1 for the latest in the 1 series (currently 1.9.1 - that may increase, the 1.9 series isn't necessarily finished yet, and 1.10 and 1.11 and 1.12, etc., even 1.9999 series are possibilities).
Or if you want a specific version, use it's full version, like 1.6.2 for example.
A Live example -
For the latest in the 1.8 series (1.8.2), right click and "Save As":
Once you download it, or as you are downloading it, you can name or rename it to its version so as to avoid confusion in the future. The one in the above example could be named/renamed:
Another advantage of using the Google hosted script is that for a live page you may skip the protocol (the
If you have some pages hosted on either an SSL (https:) or on a regular layer (http:), or both, the user's browser will fill in the correct protocol. And since Google hosts both types, it will send the required one to your users.