4 ms·

What's with that Node.js part? Even if it is part of the backend it has nothing to do with the app, so i 'll go ahead and guess either the writer is clueless,

• dpritchett 15y ago
  The writer recently went back to school to get an AS focused on OOP/Java: http://www.linkedin.com/in/jolieodell http://www.linkedin.com/in/jolieodell
• eldude 15y ago
  The seemingly irrelevant emphasis on node.js is consistent with commitment to "web technologies" (JavaScript).
• wavephorm 15y ago
  I don't think the author has any idea what anything in that article even means.
  • mcantelon 15y ago
    She's been covering Node for a year or so and even judged a Node Knockout competition. http://mashable.com/2011/03/10/node-js/ http://mashable.com/2011/03/10/node-js/ http://venturebeat.com/2012/01/30/dahl-out-mike-drop/ http://venturebeat.com/2012/01/30/dahl-out-mike-drop/ http://nodeknockout.com/judges http://nodeknockout.com/judges Here's an interview she did last year with a Node dev in which she referenced LinkedIn's work with Node for their mobile site. http://venturebeat.com/2011/12/09/node-js-rackspace/ http://venturebeat.com/2011/12/09/node-js-rackspace/
• pedalpete 15y ago
  I agree that the author has no idea about client vs. server, but reporters aren't technical, it goes with the territory. I think Prasad lead the discussion to node.js (the author journo wouldn't know to ask) so that they could talk about open sourcing tools, etc. It was a chance to get a message out. Is it possible also that node.js is providing faster response times on the same number of servers?