Batched updates

Depending on the store/action design of an app, batching updates can be a pretty useful/important perf optimization. @yoshuawuyts what are you thoughts on the best choo-like way to handle this? Would you be interested in adding a hook that would make this possible in some app-wide way (like maybe a way to provide ‘middleware’ function through which updated states were passed before being emitted to the view-rendering)? Or would you prefer for people to handle this by simply throttling individual view functions?

[anandthakker]

@yoshuawuyts I haven’t given it an actual test drive, but from a read of the code the approach looks great to me! I have a couple of thoughts but I’ll post them as issues over in nanoraf.

[yoshuawuyts]

Ooh, yeah I’ve been considering this; combined with documenting best practices on thunking views and caching routes (https://github.com/yoshuawuyts/sheet-router/issues/17) it would def be worthwhile to put an upper cap on flushing updates.

In the past for virtual-dom applications I used yoshuawuyts/virtual-raf to flush updates at 60fps; it could def be worthwhile exploring this for choo too - especially the interaction with webworker rendering would become interesting (https://github.com/maxogden/yo-yo/issues/22).

I think this should happen after the 3.0 release though; as it’s a minor tweak without practical API changes. Does this answer what you meant? Cheers!