> Some people don't seem to understand what the whole JS SPA thing is about, and it's quite strange to me. Most people understand the promises of SPAs, but th

> Some people don't seem to understand what the whole JS SPA thing is about, and it's quite strange to me. Most people understand the promises of SPAs, but there are several forces that play against everything you said: - Some websites don't need a desktop experience yet they go the SPA route. - SPAs are -in my experience- significantly harder to get right than server-rendered apps. For sites that are a good fit for "the regular old web" we are speaking about at least an order of magnitude here. - Oftentimes it is companies/products with significant resources that embark on the SPA ordeal. This usually means that they also have several teams demanding product analytics, A/B testing and what not, and hence their sites end up loaded with random shit (gtm, analytics, optimizely, facebook pixel and the kitchen-sink). For all these reasons, it takes an extraordinary (i.e: significantly better than average) team, from the developers all the way to management, to deliver on the SPA promise. As a result, most SPAs suck, and hence a lot of people cultivated an aversion to them. It really is that simple.