TE
TechEcho
Home24h TopNewestBestAskShowJobs
GitHubTwitter
Home

TechEcho

A tech news platform built with Next.js, providing global tech news and discussions.

GitHubTwitter

Home

HomeNewestBestAskShowJobs

Resources

HackerNews APIOriginal HackerNewsNext.js

© 2025 TechEcho. All rights reserved.

Greenspan: Tradeoffs of client-side rendering vs. server-side rendering

5 pointsby debergalisalmost 12 years ago

1 comment

rcsorensenalmost 12 years ago
For anyone who wants to take the &quot;Holy Grail&quot; path, I&#x27;ve been a big fan of Rendr. ( <a href="https://github.com/airbnb/rendr" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;airbnb&#x2F;rendr</a> ).<p>With a bit of self-discipline, all your views can be written out using string concatenation on the server before being sent out to the client. This means no worrying about full browser stacks, or DOM manipulation, or anything else server-side.<p>Rendr helps with that step in addition to wrapping up model fetching and re-hydration when they get sent out to the client.<p>Using something like Rendr keeps you in the full Backbone&#x2F;node ecosystem instead of the Meteor walled garden, letting you incrementally handle this instead of making a strict architecture choice to Meteor.