A poorly written SPA has worse usability than a poorly written Rails CRUD app, because your potential screw-up surface area is larger. If you have a lot of exp

A poorly written SPA has worse usability than a poorly written Rails CRUD app, because your potential screw-up surface area is larger. If you have a lot of experience writing SPAs and a team that's eager to learn, maybe you'll get everything right: server-side rendering, graceful error handling when the app plumbing fails, appropriate separation of server-side and client-side workloads, good performance on shitty connections, consistent behavior across browsers... Personally, I enjoy using well-made SPAs, but often find myself fighting against many of them because there are so many considerations that go into making them right.