| > Yet almost everything is built with a tool that's merely good enough for the task. Which usually makes it one of the right tools. I agree with you there so long as you understand which tools are good for which tasks. > we're talking about handling some http requests and someone's weekend project that managed to register a domain name. Node.js and cgi-node are not marketed as being strictly for weekend or toy projects. In fact, cgi-node is marketed as a tool that can do everything except cook your breakfast (see the last sentence of the cgi-node homepage). This just shows how badly over-marketed these products are. > What is the right tool anyways It's going to depend on the problem. Node.js's major failings are in the (arguably) poorly designed programming language and the continuous passing of callbacks. If your product can work within those constraints then Node.js might be the right choice. For most people Node.js will not be the right choice. > Bottom line is that you're getting wound up by a project that has 9 commits I don't care about how big or small the codebase is. I just care about it being marketed as a valid solution to most problems when it's really just a trap in most cases. > I think your PHP job security is safe for now, my friend. Pointless personal jab based on an incorrect assumption. I do not work in PHP and I don't see Node.js as a threat to the job security of any competent developer. |