4 ms·

Can you name a couple? I can't think of a single example like what you describe.

• Gigachad 4y ago
  Almost every google site is a SPA and work flawlessly. Spotify web works very well, even better than server side rendering as it can continue audio playback between pages. Imo the main issue with spas is they can be very fragile and don’t handle errors because they were built lazy. And since it’s all async, the spinners keep spinning forever despite the request failing already.
  • acdha 4y ago
    > Imo the main issue with spas is they can be very fragile and don’t handle errors because they were built lazy. I think that’s the key point: the more browser functionality you take over, the more of a resource commitment you’re making to support that extra code. If you’re Google or Spotify, you can easily afford that and in the latter case you have a strong argument for necessity because there’s no way to keep the music playing across page-loads. The key part is making sure that you’re taking on an appropriate level of work for your team and site. A local restaurant website should probably prioritize loading quickly since most people are looking for fast answers and the owner doesn’t want to pay to maintain a heavy tool chain which requires frequent maintenance.