>> we would need to roll our own Mustache template compiler
> I'm not sure if I understand this point but why not just use Sprockets to compile templates? Or what do they mean by 'own [...] template compiler'?
We'll be using the same partials for both server-side and client-side rendering. Its enough we have to have two sets of controllers, and two sets of models; I'm not about to maintain two sets of views as well.
No need to roll your own, there are solutions out there already: https://github.com/railsware/smt_rails, and surely others by this point
>> Views are handled via 2-way binding against rendered Mustache templates;
Ember uses Handlebars.
>> we would need to roll our own Mustache template compiler
I'm not sure if I understand this point but why not just use Sprockets to compile templates? Or what do they mean by 'own [...] template compiler'?
>> the typical SPI issue of a blank page, followed by the browser chugging on JSON and templates before finally rendering the page
In practice, both JSON and templates is usually inlined, so no additional requests are necessary on the initial page load.