2 ms·
It's because the web developer is so far removed from the hardware; we work in Typescript, which is transpiled to Javascript, which is minified, optimized and c
by Cthulhu_ 4y ago
It's because the web developer is so far removed from the hardware; we work in Typescript, which is transpiled to Javascript, which is minified, optimized and compressed before it's sent to the browser, where it's run in a JS engine in a browser in an operating system where there's a few more steps to the actual hardware.
And that's plain JS, most people don't even work in plain JS but in a framework where they don't just say "var x = y" but "publish this event into my Observable stack which triggers a state update which will eventually, somehow, update my component which will then eventually update the DOM in the browser", after which the browser's own whole stack of renders takes over.
Meanwhile in video games you can say `frame[0][0] = 255` to set a pixel to white, or whatever.
I think it's a matter of levels of abstraction; with webapps, I'd argue they've gone even further than Java enterprise applications in the 90's / 2000's.