Heh, the issue with unpoly is it does not only DOM-element swapping but also URL changing without reloading the DOM. ^.^;
It makes the concept of a per-page commander kind of breaking without some way to re-establish their connections, as it is if you want to mix unpoly and drab you need to use no per-page commanders and instead use purely only shared commanders, which is doable, just have to design with that in mind. 
Whooo!
I’m curious, does it load it up from DETS then persist it? Or does it access it from DETS on every request (much much slower)? And instead of DETS why not instead just bake it into a module?
Whooo! This will make compositing templates so much nicer!
Very useful! Can have far more shared code now without needing to make more round-trips to the client to get extra information!
Awesome!
it was easiest for me to build it and debug. And yes, I am planning to put it into module, like Phoenix.View does. But so far it works, so it can wait 