3 ms·
That makes sense. But isn't that punishing to lower end hardware users? Also aren't you moving much more data back and forth to do that?
by shiftpgdn 6y ago
That makes sense. But isn't that punishing to lower end hardware users? Also aren't you moving much more data back and forth to do that?
- jameslk 6y ago> That makes sense. But isn't that punishing to lower end hardware users? Yes, and the punishments will continue until hardware improves. More seriously, this is definitely a big trade-off. That's why page weight has been growing over time and client side metrics haven't been getting much better despite improved hardware and connection speeds. There's no free lunch. As I've mentioned in past comments, now's a great time to be a web performance consultant. > Also aren't you moving much more data back and forth to do that? Considering that usually the bulk of the frontend arrives once and then gets cached/runs continuously, I would say generally no. Server side rendering requires the page to be sent in whole on each request, unless you're doing some funky hybrid stuff with partial server rendering.