[seawlf]

I've worked on a number of SPA's over the years and I always run into the problem of getting my team to give a shit about performance. "We're not Google," they protest. Frankly for a lot of people it's the trade-off of slow client performance for development velocity. It's much easier to just throw on another state for new functionality than it is to consider what parts of the page can be static and how they can be rendered.

[andybak]

Surely if you can't produce an SPA with equivalent or better performance than a more traditional architecture then - don't build an SPA.

Or even better use a simpler solution that gives me 80% of the benefits of an SPA: Turbolinks, PJAX, intercooler.js or even a light sprinkling of good old AJAX.

Does anyone remember "progressive enhancement"?

[tacone]

Perhaps the most simple and trasparent solution to seamless navigation: http://instantclick.io/

As long as your backend is fast enough, it feels like navigating a SPA.

[thehardsphere]

See, "we're not Google" should actually mean that you care about performance more. Google can throw millions of dollars worth of infrastructure into making an app go marginally faster. Whereas, all you have is brainpower before you deploy or ship. And it doesn't take that much more brainpower to get big increases in client performance when you're starting from not-optimized-at-all. The marginal payoff is larger and the marginal costs are much smaller.