The repaint overhead is the same for every system tested. The benchmark evaluates the overhead of data book keeping for one class of problems (updating a bunch

The repaint overhead is the same for every system tested. The benchmark evaluates the overhead of data book keeping for one class of problems (updating a bunch of bindings all at once). Just because the paint time in this particular example dominates doesn't mean that the benchmark is inaccurate, as many applications using some sort of data binding-ish technique are indeed dominated by JS rather than paint time. > and as long as data binding is implemented in a sane manner, it is almost never the bottleneck. Maybe for small apps.