4 ms·
Render 100 node in browser it is less then 16ms, if you need hard logic, you can use reactive for that. Library first of all created all child deep, after that
by pyxru 8y ago
Render 100 node in browser it is less then 16ms, if you need hard logic, you can use reactive for that. Library first of all created all child deep, after that appendChild to DOM in memory, when all child and root ready and after that will be append in place on page.
- ricardobeat 8y ago> if you need hard logic, you can use reactive for that What do you mean by that? Any logic still has to execute in the same 16ms budget. In any case, it's pointless to discuss in a vacuum, I suggest you implement something like the JS Framework Benchmark [1] or DBMonster to see where it stands in fact, and then optimize from there. [1] https://rawgit.com/krausest/js-framework-benchmark/master/webdriver-ts-results/table.html https://rawgit.com/krausest/js-framework-benchmark/master/we...
- pyxru 8y agoThank you for link, i 3rd week try found it. Yes of course optimisation always in progress. I tested render 500 nodes node(simple div) and every 10ms updating 50y from them, fps was 60.