Let me give a slightly different take on it. My sense is we got to SPAs because the industry wanted more responsive and more dynamic web sites. That said, I would break down sites into one of two types; those that need/want SEO and those that don't.
For non-SEO sites (anything password protected), the initial page render is nice, but not absolutely required. Some very high traffic sites, like Facebook and Gmail, continue to do mostly client side rendering. Administrative sites like the AWS console also nicely fit into this category. For the SEO sites, server side rendering is a business need. I'm trying to think of a case where a major site that tried client-side rendering only didn't eventually come back to server side rendering (at least for the first page). Some notable examples would be Twitter and Airbnb. They tried, client-side only, but ended up rendering the first page server side. Ok, last point and I'll stop ranting ;) As for the additional HTTP request, my sense is that it's not the number of requests, but the overall latency (or time to first Tweet as Twitter would put it) that's important. Most modern sites (Google, LinkedIn, Facebook, Netflix, etc) use many services to handle a single request. What's important is that these low-latency requests don't significantly impact and may even reduce overall latency. -- Note that posts from new members are moderated - please be patient with your first post. --- You received this message because you are subscribed to the Google Groups "ClojureScript" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojurescript+unsubscr...@googlegroups.com. To post to this group, send email to clojurescript@googlegroups.com. Visit this group at http://groups.google.com/group/clojurescript.
