News for hackers. Stuff that matters.
Re:Node.js is Backwards by jrockway on Monday June 13, 2011 @08:44PM (#2651360)
NodeJS is great for applications with a lot of clients, but not for CPU intensive apps.

Well, you do with node what you do with anything: if you have 4 CPU cores, run 4 copies of your app. Problem solved.

Re:Node.js is Backwards by mcantelon on Monday June 13, 2011 @10:10PM (#2651537)
With Node you have to manage the 4 cores if you're doing something where they need to communicate.
Re:Node.js is Backwards by ankrgyl on Monday June 13, 2011 @09:34PM (#2651473)
That works really well for handling requests for HTML pages, because they tend to render independently of one other. However, you run into trouble when you to make "Nodes" communicate, and the comment that the article is addressing specifically mentions interprocess communication.
Re:Node.js is Backwards by sausagefeet on Monday June 13, 2011 @09:00PM (#2651397)
Clearly it's not that easy unless you plan for it from the beginning. One benefit of Erlang is that you have to structure you code like a distributed application. You can mess that up, but it's harder.
Re:Node.js is Backwards by tibbe on Tuesday June 14, 2011 @06:33AM (#2652460)
This allows you to serve more clients simultaneously, but not to serve any given client faster i.e. you get higher throughput but not lower latency.
Re:Node.js is Backwards by thesz on Tuesday June 14, 2011 @06:08AM (#2652412)
Imagine your app has 16GiB of precomputed tables in memory...
Re:Node.js is Backwards by strmpnk on Tuesday June 14, 2011 @10:51AM (#2653206)
Node.js has a heap size limit. One of the biggest weaknesses IMO well before people complain about CPU cores.