Very cool, @arunoda
For famous-views, I had to make sure that template materialization / destruction wouldn’t block animation frames, i.e. couldn’t run continuously for more than a few ms per frame. So I’ve been experimenting with a virtual DOM for Blaze - that simply queues DOM updates and dequeues with a timer (with room for further optimizations in the future).
I haven’t mentioned it before because I haven’t decided yet how far to take, i.e. it supports evertyhing Blaze does but, how would we want to handle the regular dev workflow for events, lifecycle callbacks, etc (which DOM should they have access to and what should be supported). What’s more exciting though is that it opens the way to run a lot of things inside a web worker.
Also, from what I understood from your video, it looks it would work with the template caching with no changes. As you know I’m a big fan of Blaze and squeezing out the best possible performance from it is awesome :> Looking forward to more updates on this.