4 ms·
> One of the arguments for a SPA is that it provides a more reactive customer experience. I think that’s mostly debunked at this point That's not true. You abs
by cyberax 2y ago
> One of the arguments for a SPA is that it provides a more reactive customer experience. I think that’s mostly debunked at this point
That's not true. You absolutely can make edge applications faster than anything running server-side. A great example is Linear, it can switch between issues within 100ms (it even supports hjkl keys for navigation!).
But this requires you to be EXTREMELY careful. In case of Linear, they're using a sync engine to replicate the data onto the client side, rather than doing the request/response model.
- JodieBenitez 2y ago> A great example is Linear, it can switch between issues within 100ms (it even supports hjkl keys for navigation!). That's nothing special and definitely easy to achieve with a server-side backed MPA.
- cyberax 2y agoA triple handshake to a datacenter across the US is already ~80ms. It can be mitigated with HTTP2/3 but that still leaves you with not that much time to serve the request. It's certainly doable, but not at all straightforward to make it reliable. A local app, on the other hand, does not depend on the network latency and the server load.
- deleted 2y ago[deleted]
- JodieBenitez 2y agoBut then... if no network latency I would expect much better than 100ms.
- cyberax 2y agoIt often is. I'm just saying that even for pretty complicated cases it's still within 100ms.
- 65 2y agoA few more examples of good SPAs are SoundCloud, Twitch, and YouTube. They all have the players move between interactions, which (generally) is better UX. Soundcloud in particular, if they didn't have the persistent player while browsing the site would be nearly unusable.