7 replies

1. bkardell 16 min later

   @zachleat what do you mean hiding slow servers here?

   1. Zach Leatherman 19 min later

      @bkardell the data services/backend/etc

      1. bkardell 28 min later

         @zachleat I _think_ you're saying that the fact that _something_ is rendered takes a lot of pressure off those things performing? As opposed to those being server rendered and the page just being hung while the data/services backend stuff is happening? Is that right?

         1. Zach Leatherman 1 hr later

            @bkardell yeah! absolutely—you said it better than I 😅

            1. bkardell 2 hr later

               @zachleat that's interesting, because it simultaneously seems to highlight where the bottleneck is and you'd think get it lots of investment. Maybe those pages would otherwise render not a lot until all those spinners were done minus some round trip latency? Or more likely if that was the option, they just wouldn't be on the web maybe?

2. Evan B🥥ehs 1 day later

   @zachleat hot take for the DMs of static site generator man... But I disagree.

   I mean, my server can process requests in as little as 1ms, but the network overhead of what... 80ms minimum? Means a performant client side router will win. Not to mention, whenever you click a link without that routing the browser needs to redo it's CSS JavaScript ect shenanigans.

   Look, my point is that for *applications*, CSR can be good, so long as it's respectful of bundle size, is optimised, and has SSR

   1. Zach Leatherman 1 day later

      @eb reminded of this classic conversation https://twitter.com/jaffathecake/status/1433317536754458628

      for sure there is more nuance to be had here