Here’s the deal: Some of us are careful about cookies. You might say overly paranoid, but whatever. I only allow cookies by whitelist. This can cause problems when I’m using a site for the first time, as I may have to allow cookies for a few domains, but it’s not a problem for sites where I actually have any interest in allowing cookies. And yes, I know there are extensions now that I can use that will simply delete cookies after a short time if I don’t whitelist, but again that’s not the point. Anyway it’s usually not a problem to enable cookies for the domains I care about. It’d be easier if some version of Firefox a while back hadn’t changed things so it cared about whether I’m using HTTP or HTTPS as the protocol, in which case I often have to set an exception twice.
Disabling cookies ought to prevent proper logins; I accept that. I can see other reasons it could be an issue for certain functionality. What it should not do is prevent the website from functioning entirely, or worse, reload over and over as I’ve sometimes seen. That’s astonishingly bad behavior.
And usually this is only happening because of some simple check early in said script to try to detect a browser or some crap. They’re not even using the capability, but checking for it when it’s not allowed WILL throw an exception which WILL cause problems if you don’t freaking catch it!
The target of this rant, by the way, is twitch.tv. I just followed a link there only to be greeted by the Nothing.
Get your crap together, guys. You’re an embarrassment to the profession.