3 ms·
> so that it doesn't have to do any expensive VDOM diffs. I am wondering, how is it possible that such non-expensive algorithm is more expensive than many VDOM
by localvoid 8y ago
> so that it doesn't have to do any expensive VDOM diffs.
I am wondering, how is it possible that such non-expensive algorithm is more expensive than many VDOM libraries in this benchmark[1] ?
1. https://rawgit.com/krausest/js-framework-benchmark/master/webdriver-ts-results/table.html https://rawgit.com/krausest/js-framework-benchmark/master/we...
- cztomsik 8y agoPlease note: 1. benchmarks have zero information value 2. be careful about wording, react does effective DOM update, but effective does not always mean fast - what I mean is that compiled templates are usually much faster than doing vdom diffing along with all of that destructuring and other unoptimizable (prepack might help, but it's far from being usable) stuff
- localvoid 8y ago> 1. benchmarks have zero information value Statements without any proof is more valuable than "benchmarks with zero information value"? > what I mean is that compiled templates are usually much faster than doing vdom diffing If they are usually much faster, why it is so hard to make them perform faster than vdom libraries in this benchmark? Or maybe any other benchmark, please just show me something that I can measure.