title: pjax or client side MVC?
body: <p>i have to start a new project, a webapp with lots of forms and screens and i really don't know which technology fit best. The application is an ERP like app, with very few animations and lot of forms. The goal is to reduce at minimum reloads and waiting time, it has to be as close as possible to a normal desktop app (a lot of work to look like a marvelous VB6 app :-)</p>
  
  <p>On the one hand we have client side MVC (backbone). It's cool to have all the code running on client but in my mind this implies repetition of lot of code (for example all models definitions) from server (PHP + Fuel). Sure once loaded all the informations task like paginations or grid work without any delay but it also present some problems of synchronization (other users can change data and i have to manually invalidate data on client).</p>
  
  <p>On the other hand we have pjax. The idea is to make all the templating and so on on server, just implement a logic to return the page without the frame for pjax request or full page on new requests. No code duplication, very simple client side.</p>
  
  <p>I've read the the story <a href="http://37signals.com/svn/posts/3112-how-basecamp-next-got-to-be-so-damn-fast-without-using-much-client-side-ui">from basecamp</a> and <a href="http://engineering.twitter.com/2012/05/improving-performance-on-twittercom.html">from twitter</a> and both the point make sense to me. You can't relay on visitor computer (features, performance ...)</p>
  
  <p>The more i think about it the mode i like pjax over MVC, but maybe i'm missing something. Which  are the MVC advantages over pjax or pjax disadvantages over Client side MVC ?</p>
  
  <p>Thanks a lot</p>