3 ms·
I am not sure you are ever going to get your benchmark with fully written apps, it's a lot of effort going both ways to build it out twice. With pure DOM, trav
by kinlan 11y ago
I am not sure you are ever going to get your benchmark with fully written apps, it's a lot of effort going both ways to build it out twice.
With pure DOM, traversing the DOM isn't the issue, you can keep references around if you really need it, or indexes or any other number of abstractions to make it perform well because you probably wouldn't build it any other way and you probably would in most cases end up with a set of primatives that do that same type of batching the updates.
- i_s 11y agoYeah, but this is significantly worse than performance comparisons that have already been done. See here for example: http://elm-lang.org/blog/blazing-fast-html http://elm-lang.org/blog/blazing-fast-html TodoMVC is way more realistic because items are actually edited, you are not just infinitely adding DOM elements. (Why would you even do that, instead of just showing the number of elements that can fit on the screen, then just reusing those?).
- wubleduble 11y agoI wouldn't trust elm-lang articles. They are very dishonest and misleading. Write an app with 10 nested sets of tabs to see why - you will quickly realize what I'm saying after going through the documentation and talking to the elm people on irc in your attempt.