Google's CDN is nice, but it's not 100% reliable for all users. It occasionally fails to load for me. Other users have had trouble with it due to sloppily-configured networks, and some may prefer to block external scripts by default.
It's one more possible point of failure. It would be preferable if Stack Exchange didn't depend on it.
If you don't want to stop using it, consider adding a fallback if it fails to load. Something like this:
<script src="https://ajax.googleapis.com/ajax/libs/jquery/1.7.1/jquery.min.js"></script>
<script>
if (!window.jQuery) {
document.write('<script src="https://cdn.sstatic.net/stackoverflow/content/js/jquery-1.7.1.min.js"><\/script>');
}
</script>
2024 Update: there is no longer any benefit to using Google’s CDN, because browsers have implemented cache partitioning to prevent resources that were cached for one website from being reused by other websites. Stack Overflow has implemented some kind of fallback mechanism that loads the script from their own CDN if it fails to load from Google’s, but this doesn’t kick in until an original request has timed out, which can be a very bad initial experience for fresh visitors. Using Google’s CDN has no upside, while the fallback adds complexity without entirely mitigating the problem, and the asset is already on Stack’s CDN. Drop the Google. It’s cleaner.