Well, not so fast. Not all pages should be rendered client side. Some pages need to be indexed by search engines, and they need to be rendered on the server. St

Well, not so fast. Not all pages should be rendered client side. Some pages need to be indexed by search engines, and they need to be rendered on the server. Stuck. With a non-JavaScript framework, duplication of code is inevitable. Why can't you just have the server serve up the raw data using a simple (RESTful) interface, then place all your logic in the client? The search engines can index the restful interface... All the rendering intelligence can live in the client. If you do this, the server code doesn't need to be javascript and hence doesn't need to be node.js. The real evil, IMHO, is server-side html templating, which I think people will move away from in a few years.