>We're not rendering html client-side for fun. Everyone I know who is doing it is doing it because "that's the future". No logical or technical reason at all,

>We're not rendering html client-side for fun. Everyone I know who is doing it is doing it because "that's the future". No logical or technical reason at all, just following the current fad. >It makes the UI more responsive, while keeping the overall architecture more simple It does neither of those things. Most javascript apps are much slower than the equivalent app using server side rendering of html. Look at how incredibly slow and clunky twitter is for example. The architecture of a typical fad javascript app is a nightmare compared to virtually anything else, super crazy "enterprise" java monstrosities are the only things I've seen that are more complex. >We can (and we do) have separate teams working on client/server. It wasn't that easy before. It could have been, we have that. Our client team does html, css and javascript. The server team does haskell and postgresql. The only thing you need to do this is a template engine that separates code from markup.