3 ms·
If there was one comment or tweet that lead me to follow him, it was this [1] "1ms is an eternity for computers" When was the last time you heard a Web Develo
by ksec 4y ago
If there was one comment or tweet that lead me to follow him, it was this [1]
"1ms is an eternity for computers"
When was the last time you heard a Web Developer, frontend, backend or web tooling Dev state that? [2] It is always, oh the network latency dominate, or the DB response time dominate. It is only one tenth of a second ( 100ms ) it doesn't matter. It is fast enoughTM.
[1] https://twitter.com/jarredsumner/status/1477775398700158980 https://twitter.com/jarredsumner/status/1477775398700158980
[2] Actually Nick Craver does that a lot during his StackOverflow era.
- lewispollard 4y agoMore web developers need to try out game development, it's a similar enough domain in terms of rendering UI and being responsive, but there's absolutely no tolerance for the kind of time wastage that web developers seem to accept as a given.
- Cthulhu_ 4y agoIt'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.