The thing about SJR is that it lends itself much better to progressive enhancement: if you need/want to present a page which also works without JS, that means t

The thing about SJR is that it lends itself much better to progressive enhancement: if you need/want to present a page which also works without JS, that means that you need to be able to render the page on the server, which means that by using SJR, you can easily reuse that same view code that you already need to have for the non-JS clients. Of course, as JS on the server becomes more and more wide-spread, you might as well just use the same templates at both ends, but it' still more infrastructure than treating the client JS as just part of the view. I discussed this back in 2011 on my blog: http://pilif.github.io/2011/04/ajax-architecture-frameworks-and-hacks/ http://pilif.github.io/2011/04/ajax-architecture-frameworks-...