> Can you please talk more about this? Average Joes want spinners, buttons, draggable stuff, toggles etc. that don't lead to a page load everytime you press th

> Can you please talk more about this? Average Joes want spinners, buttons, draggable stuff, toggles etc. that don't lead to a page load everytime you press them. Sure, you can say that "well just make a multipage app with some jquery". But at some point you're just approaching a SPA with SSR support. Imagine facebook's chat but everytime you hit enter you had a full page reload :D > In reality, multipage applications are faster than single-page ones. I agree. They are faster for a single user when the usecase is a semi static page like a forum. However, the SPA + API model makes stuff easier for the backend side and allows that average Joe UI stuff. It scales well to millions of users. The thing is, it's not about you. It's about everyone. We want to build services that please the majority and backends that stay up when the majority is logged in. Also, it really isn't possible to build realtime/dynamic stuff with a "let's render some HTML on the server" mindset. How do you do realtime chat? Realtime games? How do you do a collaborative text editor? and so on. JSON/SPA/AJAX are not there to so your static forum page loads fast. They are there because of the next generation of the web.