3 ms·
A browser cannot always recuperate when JavaScript fails to arrive - what should it do at that point? A recent example: the outage of googleapis.com CDN caused
by untog 15y ago
A browser cannot always recuperate when JavaScript fails to arrive - what should it do at that point? A recent example: the outage of googleapis.com CDN caused problems on many sites using JavaScript hosted there all because OpenDNS blacklisted the domain as a phishing domain.
Well, that's just bad planning on the part of people that are relying on a third party service for a core feature. Always have a backup for remote CDNs.
If you've done that, non-JS functionality is a tiny, tiny edge case. In an ideal world we would all handle it, but I just don't think it's realistic to expect developers to set the time aside for it.