title: Server-side vs client-side MVC in web apps
body: <p>I've recently found an interesting alternative to the ASP.NET MVC that I currently do: static HTMLs with advanced JavaScript doing service calls (most examples use OpenRasta). For example see <a href="http://javascriptchicago.com/talks/jmvc_may09/jmvc.html" rel="nofollow noreferrer">this</a> or <a href="http://theruntime.com/blogs/jaykimble/archive/2009/06/01/clientscript-as-the-view-controller.aspx" rel="nofollow noreferrer">this</a>.</p>
  
  <p>Personally I always had a feeling that web apps need to move towards JavaScript frameworks. To me it feels the code in MVC to wire up client/server side validation (and other things like translating business models into view models) seems awkward and a bit unnatural. Actions that basically takes data and return JSON, or actions that just do "return View()" is a clear indication of that.</p>
  
  <p>However, the question is not what's better - this is kind of discussion that I don't think SO likes ;-) My question is: have you tried both? Would you suggest to invent into learning jMVC and alike? Any good articles on the subject? Pros and cons? For example, <strong>big</strong> cons in my opinion is a very strong SOC, a ready-to-reuse service, etc.</p>
  
  <p>To sum it up: what direction would you suggest to move further?</p>