We’re seeing numbers on mobile that suggest that JavaScript can be faster than native end to end due to I/O costs for loading the code from disk. On web this matter even more because the network cost. JS haters need to embrace I/O over CPU perf if they want to win.
-
-
Exactly. I think it goes beyond that. There is an elitist associated with those communities that consider the JS approach is purely subpar. Web assembly will hopefully surface the bitter truth of this tradeoff.
-
Yeah. The whole "drive-by web" as a synonym for crap really misunderstood what makes the web tick. The web has an extreme perspective on performance where a "slow boot" is counted in a small number of seconds, and we're paring it down to sub-second.
-
And somehow this is all done while parsing, compiling and executing a dynamic language. It's not like other ecosystems can't do it, it's just that they haven't tried anything even remotely similar.
-
I think it has not seen as important. High-end games has gotten a free pass where as small peripheral games that need this are seen as low-end even though it’s big business.
-
High end games have literally minutes-long loading screens. They've been given a pass as responsive experiences we should strive to reproduce despite that. Pretty sad.
- 1 more reply
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.