On Wed, Dec 8, 2010 at 7:37 PM, Vikram Mavalankar (vmavalan) < [email protected]> wrote:
> Hi, > > I am trying to collect resources to evaluate the pros/cons of server-side > JS (e.g., using node.js) vs. client side JS. > Any thoughts? > It's not really a matter of server side vs client side - these two do different things and both have their place. In the case of node.js, the server side js does the same as you would normally do with .net/ruby/php/..., and so it is more a case of these vs javascript on the server. Not looking at speed, scalability etc, things speaking for using js on the server as well as on the client (not instead of) are - reuse of code, eg. validation of fields, templating - only need to know/use a single language/technology If you mix server side rendering with incremental updates using xhr/templates etc, things get really interesting. Sean
_______________________________________________ JSMentors mailing list [email protected] http://jsmentors.com/mailman/listinfo/jsmentors_jsmentors.com List Archive: http://jsmentors.com/pipermail/jsmentors_jsmentors.com/
