It's the old 'blame the dev not the compiler' quip. When I was in undergrad learning to code, before web browsers, if students blamed the compiler for their err

It's the old 'blame the dev not the compiler' quip. When I was in undergrad learning to code, before web browsers, if students blamed the compiler for their errors the profs just didn't care. If the compiler crashed the OS while compiling it was still the student's problem to figure it out. Now you frequently hear intelligent devs complaining about how FF is slow compared to Chrome when loading website X. And here I am simply amazed that web browsers don't just crash constantly from the reams of dumpster trash they're forced to injest. It's developers that have turned the web into a stinking pile of bloated code, but yet we continue to blame the interpreters(i.e. browsers).