I feel like I&#x27;m about to wander into a debate that&#x27;s over my head, but I don&#x27;t see why one computer (or one small group of computers) should be responsible for doing work that could easily be performed in a more distributed way by people&#x27;s browsers, if only because it&#x27;s cheaper to offload that work onto the client and leaves less ways to crash the server-side application.<p>I&#x27;m with you 100 percent when it comes to &quot;I can&#x27;t read this text document because it needs 45 JS libraries to render,&quot; that&#x27;s stupid. But it&#x27;s probably stupid because it&#x27;s over-engineered, not because it uses the browser.<p>I feel like this is going to become a bigger and bigger debate in the coming years, and I&#x27;m eager to be proven wrong, or at least understand the other side. But if I&#x27;m building the next great web-based spreadsheets application (I&#x27;m not), my immediate and overwhelming success is going to be WAY easier to manage if the majority of my code is being executed on the millions of computers calling in to use it, not on the three servers running in my auto scaling group. Why WOULDN&#x27;T I pick that option?