3 ms·
The focus on JS benchmarks is becoming ludicrous. By far the biggest performance issue is DOM/CSS layout. JS is so fast on all browsers that the performance dif
by Joeri 11y ago
The focus on JS benchmarks is becoming ludicrous. By far the biggest performance issue is DOM/CSS layout. JS is so fast on all browsers that the performance differences don't matter at all anymore, except for initial load (and if you're loading that much code on initial page load, you should re-evaluate your architecture).
- Klathmon 11y agoI agree 100%, but they were asking for a place with JavaScript benchmarks, so I gave my favorite.
- _greim_ 11y agoModern frameworks have worked hard to mitigate DOM bottlenecks, thus pure JS bottlenecks are now a thing. Especially data-rich applications. Reflow and paint performance is still an issue but the focus on JS is worthwhile.
- Joeri 11y agoHave you measured this? Do you actually build or use specific apps where the dominant factor is JS execution time and not layout or network time?
- _greim_ 11y agoYes. String-processing tweets (linkify and emoji-insert) and crunching numbers for time series line charts were two areas where we saw some lag. It was React so these bottlenecks were happening during virtual DOM rendering. And realizing GP was talking about client-side, but also don't forget server-side, where DOM doesn't exist and the hyper-focus on pure-JS perf is much appreciated.