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.
* http://www.thewhir.com/web-hosting-news/010612_Thousands_of_...
There are more reasons JavaScript indirectly failing in a browser: http://christianheilmann.com/2011/12/06/that-javascript-not-...
So generally, it makes sense for a site not to depend on JavaScript for a core basic experience.
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.
"Now, I realise... the fact that I've purged Facebook from my view of the internet is partly to blame, but I bet I'm not the only one on HN to have done this."
Still, if you happen to not have a Facebook account or don't want to associate yours in any way, good luck!
I figure we're at the point on the web where Javascript et al would be expected in your browser, but even if you don't sign up for that belief, at the very least you should understand you're part of a small minority and sometimes have to make concessions.