Brian M Hunt

Well. That's unexpected: [Rendering faster by hiding DOM elements instead of removing them](http://jimkang.com/articles/browser-disapproval-of-frequent-dom-removal/) (Or at least it would've been until I started looking into this problem) > Rougly 80 ms...

Thanks @krnlde – We construct the `nodes` (being nodes corresponding to an item in the given list at [getNodesForIndex](https://github.com/brianmhunt/knockout-fast-foreach/blob/master/index.js#L263)), so my expectation is that there should never be holes in...

@cervengoc I rooted through React and Angular and didn't see any references to `removeChild`, so I'm guessing they must be doing something different. But it's just a guess. :smile: The...

Thanks @krnlde – Great finds re. the `removeChild` ... my searching skills leave something to be desired! :wink: I think it's definitely worth checking out the performance of a batch-move...

Thanks @cervengoc Lazy-remove would be, at its most basic, a two-step process: 1. Set `display: none` in one animation cycle; to deals with the rendering 2. Remove the elements in...

@sacredMonster Please add a jsFiddle. As a support question you may better results on StackOverflow.

@cervengoc Yep, behaviour when modifying `bindingContext` would be not well tested for many bindings. I would classify this as "experimental". The nested re-use is definitely an issue, so I would...

An alternative, (that may or may not be) worth considering, is forking fast-foreach and creating another binding for simple cases, that extends the `FastForEach` class. Just in case we're getting...

The `with` / `using` bindings are in tko. I think `foreachUsing` works, unless we thing of something cleverer. 😄

Fixed (I believe) as of v0.5.4? :)