4 ms·
Knockout's perf on large re-renders is below average: http://mathieuancelin.github.io/js-repaint-perfs/knockout/ http://mathieuancelin.github.io/js-repaint-perf
by EvanYou 10y ago
Knockout's perf on large re-renders is below average: http://mathieuancelin.github.io/js-repaint-perfs/knockout/ http://mathieuancelin.github.io/js-repaint-perfs/knockout/ It also doesn't allow you to use programmatic render functions, nor does it have server-side rendering.
Vue 2.0's vdom implementation is mutation resistant - as long as you don't replace the element directly controlled by Vue (same as 1.0), the rendering will not run into problems. If you are really concerned you can always create a custom component that returns an empty element so that you can do arbitrary manipulations inside.
- nightski 10y agoThat's exactly why I am switching away from Knockout. I loved every minute of it, but there are features I simply can't deliver on because the perf is too low. There are all sorts of hacks I could do to get around it but that is really going to slow me down. TBH It's not really the rendering that is slow in my experience. It's the fact that every binding attaches an event handler to the DOM. This can take up to 10s for a reasonably sized grid in IE.