4 ms·
and think of what Chrome did for JavaScript performance I think that's partly what contributed to this slowdown --- faster JS execution to a browser is basical
by userbinator 8y ago
and think of what Chrome did for JavaScript performance
I think that's partly what contributed to this slowdown --- faster JS execution to a browser is basically like faster hardware to a native app, thus reducing the impetus to optimise the JS code itself. Imagine if hardware wasn't getting any faster (we're close to that already) and browsers still used regular intepretive JS execution like IE6 instead of JIT'ing. If browsers don't execute JS any faster, then web app developers would have to do a lot more optimising to get even acceptable performance, and perhaps we'd see some more interesting tricks and knowledge develop.
- dvfjsdhgfv 8y agoThat's correct. On the other hand, I see many people sheepishly accepting slow page loads and overall unresponsiveness of today's web apps because - apart from a few slim ones - the majority seems to be equally sluggish, loading tons of JS, webfonts (before the page gets loaded!) and what have you. Many people somehow got convinced that it has to be that way.