3 ms·
If you're really that paranoid, monitor and verify. If there are issues, you can change hosting optins. You don't mitigate risk by doing everything yourself.
by teej 18y ago
If you're really that paranoid, monitor and verify. If there are issues, you can change hosting optins. You don't mitigate risk by doing everything yourself.
- ars 18y agoWhat? How are you supposed to monitor and verify that google is up from the point of view of the client? If you do it locally it's either fully working, or fully down, and you don't have javascript errors when parts work and parts don't.
- Encosia 18y agoIf you're worried about Google's reliability, you could always test for typeof(jQuery) !== 'undefined' before assuming it had loaded. Then, you can inject a script element referencing a copy of jQuery on your server if it hadn't. In practice, I would think the chances of Google's entire CDN going down are the very least of your worries though.
- ars 18y agoThat's quite an interesting idea, but I'd be worried about it running too soon, the browser doesn't give you a "gave up on downloading something" event. Google goes down more than you think - it's not usually that google itself is down, but rather that DNS didn't look them up, or some anoying routing issue. It's happened to me, so I know it does happen.