The major argument is that if you build an SPA, you'll do a bad job. So... don't do a bad job? This completely misses the major benefit of SPA: reusable web co

The major argument is that if you build an SPA, you'll do a bad job. So... don't do a bad job? This completely misses the major benefit of SPA: reusable web components made with the latest version of JS with a framework that updates the DOM from a view model. I guess you could accomplish that without SPA, but I'm pretty sure we're all here for the frameworks/es6/typescript/compnents, and SPA is just the deployment model. A deployment model which allows all that to happen with a fairly short initial load if you're doing things right. If you're loading multiple megabytes in your first chunk in 2018, then you're doing it wrong. All that said, are you making an 'application', or are you making an informational website? If you're making a simple website, SPA is just silly. If you're making an application, and it just happens to be deployed via a browser, SPA, and more importantly, the things I mentioned going with it, are a huge productivity and organizational boost.