>Toys are very fun, and I would never try to take that away from anyone, but (in my opinion) there are waaay too many people pushing Node for production work that should know better, and that's the scam.
Walmart used it to deal with much of their Black Friday traffic with no incident and with modest hardware. Node hasn't hit 1.0 yet, but the major API changes are now in the past. So what, specifically, do you see as immature about the project?
All points for working code, and let me confess ignorance up front right now.
Really my irk comes down to something along the lines of, "Well why not write it in Go or something? Why JS?" and thinking that the only really good answer to that is "Well, we really like JS."
You should read this interview [1] and watch the talk [2] by node's creator Ryan Dahl to get a better understanding of where it comes from. There was much more to it than "we really like javascript" (tldr: single-threaded, evented, dynamic, freedom to write new I/O apis, backed by huge companies, well known).
Are you talking about cooperative multitasking (vs preemptive)? Though modern OSs went a different route, it clearly works very well for servers and node.
Walmart used it to deal with much of their Black Friday traffic with no incident and with modest hardware. Node hasn't hit 1.0 yet, but the major API changes are now in the past. So what, specifically, do you see as immature about the project?