title: Single Page Apps vs PageAx
body: <p>Single Page Apps are well known.  But PageAx seems to be less well known.  I stumbled across it by accident in learning MVC and it has worked quite well for me so far.  </p>
  
  <p>(Note: I am aware that this is a topic which may be regarded as "not answerable" and "should be closed" yet I feel this is an important topic which has not yet been covered.  Note that this is Single Page Apps vs. PageAx (not Ajax).  I am looking for benefits/disadvantage type discussion.  I am making up the name "PageAx" as I have not found a better term for it.)</p>
  
  <p>SPA - communication with controller via Ajax and returning Json.</p>
  
  <p>PageAx - communication with controller via Ajax and returning partial views which replace divisions.</p>
  
  <p>Here are the benefits of PageAx as I see it, over SPA's:</p>
  
  <ol>
  <li><p>Little to no JavaScript on the client.</p></li>
  <li><p>I find Partial Views very easy to write on the server side.</p></li>
  </ol>
  
  <p>Benefits of SPA over PageAx:</p>
  
  <ol>
  <li>I can't think of any.</li>
  </ol>
  
  <p>Disadvantages of PageAx over SPA:</p>
  
  <ol>
  <li><p>Slightly larger payload (but I doubt it would be discernible by end user.)</p></li>
  <li><p>I can't think of any other.</p></li>
  </ol>
  
  <p>Disadvantages of SPA over PageAx:</p>
  
  <ol>
  <li>Seems like the amount of JavaScript and required libraries present a fairly large learning curve (i.e., more so than MVC.)</li>
  </ol>
  
  <p>So to re-iterate the question, are there any advantages to SPA over PageAx?  The basic reason for the question is that I am starting yet another web project and need to decide which way to take it.</p>