Ok, trying to maintain my commit streak, so I'm going to talk about features of the framework that you might find interesting.
WildflowerJS has data pools. They're an alternative reactive path for when you need high throughput like for games or simulations. It shares the same shape as lists, but is pull-reactive instead of push-reactive.
Basically, you either make your reactivity explicit with a markDirty() or you have a tick() that flushes all changes on the next rAF. Here's a diagram from the documentation showing the difference between list and pull reactive paths.
The nice thing is that if you have a simple list, you can still use pools to get the most performance for it, with just a smidge more work.
commit 75f4c6b