Shouldn't a goal be to mitigate the number of possible failures which can bring down your site by reducing the number of single points of failure?
1. If you're still using HTTP 1.x, sharding assets across origins lets the browser load them in parallel (if set up correctly). You can generally load just 6 assets in parallel per origin, and sharding is a way to get around that limit.
2. A library like jQuery is so popular, and is so often served from googles CDN, that chances are a user already has it in their local cache from when they downloaded it on some other site.
That said, yes - the downside is more surface area that might go down.
In fact, right now YouTube loads far quicker than it has for the last seven to ten days, where it would take ages to load any YouTube page.
When we proposed adding a daily reboot to cron, the tech lead (which encouraged practices which lead to this low quality software) retorted that "this in not Windows, it doesn't need constant reboots", totally missing the point that just using Linux doesn't make you a developer of reliable software.
That's why the smart money defaults to 8.8.4.4...
I did hear youtube having 503 errors.
North Korean cyber attack anyone?
[0] https://www.google.com/appsstatus#hl=en&v=status
[1] https://www.google.com/appsstatus#hl=en&v=issue&sid=1&iid=d4...
Or maybe Samsung's announcement of a 'fold out' phone?
Or the Ted Cruz news?
It's a busy morning.
I think google is pretty good about engineering no global single points of failure; all updates are rolled out to only a fraction of users/machines at a time, etc.
Edit: Everything working fine for me again.
9/12/2017 @ 10:27 AM +MST (Time services reported back up according to status page)