3 ms·
Oh, interesting! Thanks for sharing. But there still is a little bit of server load, whereas front-end has 0. Honestly, unless you're serving billions of pagev
by jbob2000 9y ago
Oh, interesting! Thanks for sharing. But there still is a little bit of server load, whereas front-end has 0.
Honestly, unless you're serving billions of pageviews on a very tight budget, I'm not really sure how much of a savings we're talking about here (server side vs. client side rendering).
- nathan_long 9y ago> But there still is a little bit of server load, whereas front-end has 0. That's true. OTOH, using a front-end framework has downsides, too. You have another framework involved, a big pile of JS that must be downloaded, more build tools, maybe you need to render server-side anyway for first page load... > I'm not really sure how much of a savings we're talking about here (server side vs. client side rendering) Yeah, me either. I think "what's the easiest way to get & maintain the desired user experience?" is probably the best question.
- ccachor 9y agoWell, Angular has a very heavy initialization penalty, enough that I know of a few companies that ditched it for React. I'll also add, as your front-end becomes more complex and uses a number of different libraries, the bundle becomes huge. There's ways around this of course, but some of pure JS stuff can get ugly quick.