
- Finally in 2012, Twitter reversed course by passing more of the rendering back to the server.
- On the server side, it provides an initial render of the page, and data could be provided through Node.js or through REST API calls.
- A JavaScript-based client fetches the data from the API server and renders the Twitter.com experience.
- The user’s browser runs no JavaScript at all until after the initial content, rendered on the server, is visible.
- The initial state is passed to the client side, which also loads the framework to provide further client-side rendering that is necessary, particularly to “rehydrate” or update the server-side render.

@techjunkiejh: “A history of #JavaScript across the stack #angularjs #nodejs” open tweet »