One of the promises of node.js (that I&#x27;ve not seen pan out really in practice since) that got me interested 4-5 years is the ability to render a web page on server or on browser using same codebase. Take as an example a heavy codebase like Yahoo! Mail or Gmail. Notice how slow Gmail especially is from login to &quot;ready state&quot;? Now imagine if the first page of your inbox was rendered server side and sent as normal HTML markup. If it was designed well, the JS would progressively load after that and if for example I click compose before that JS was loaded yet, the click would be treated as a normal click and it&#x27;d round trip to the server and then render the compose view and send me back the new page. If the JS had loaded, it&#x27;d just be rendered in browser like normal. Doing tricks like this can massively increase the perceived responsiveness of web apps. I&#x27;ve seen prototypes of Yahoo! Mail built like this and man they are so fast, but sadly doing this is well is very complicated and node.js never actually helped as much as it promised too. Don&#x27;t get me wrong, what I described above I&#x27;ve seen done in production code, it&#x27;s just it was a very manual and slow process and node.js never did that much to help, IMHO.