4 ms·

It infuriates me when I see people complaining about how slow they think JS/HTML/CSS is as a developer platform, or how terrible it is to use a JS framework, wh

It infuriates me when I see people complaining about how slow they think JS/HTML/CSS is as a developer platform, or how terrible it is to use a JS framework, when the real cause of slowdown for 99.9% of the web is garbage like this. Modern web browsers can preload resources and compile and run JS incredibly quickly. But even the best optimization efforts fail when sites are loading thousands of scripts from hundreds of different domains. And yet still I see developer advocates from Google on Twitter trying to shame people for using React, blaming them for the web's failure to dislodge native apps. It's utter bullshit.

5trokerac3 9y ago
Now you know how Flash developers felt when everyone was saying it was a buggy platform, because so much of the dev community never did active debugging. I ran the debugger version of the player and would get error alerts all over the web - for things that should have been caught with a try/catch or basic variable checking - even on some of the most prominent web apps of the time. 99 out of 100 times, that was the reason for an app crashing, not the player itself.
- f137 9y ago
  this
  - seanp2k2 9y ago
    But now everyone has a JS debugger, so everyone is a critic :)
AndyMcConachie 9y ago
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).

5trokerac3 9y ago

Now you know how Flash developers felt when everyone was saying it was a buggy platform, because so much of the dev community never did active debugging. I ran the debugger version of the player and would get error alerts all over the web - for things that should have been caught with a try/catch or basic variable checking - even on some of the most prominent web apps of the time. 99 out of 100 times, that was the reason for an app crashing, not the player itself.

f137 9y ago
this
- seanp2k2 9y ago
  But now everyone has a JS debugger, so everyone is a critic :)

AndyMcConachie 9y ago

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).