2 ms·
They are both providing a model for performing concurrent work. Erlang is quite good at writing distributed applications, but not everyone is writing distribut
by sausagefeet 16y ago
They are both providing a model for performing concurrent work. Erlang is quite good at writing distributed applications, but not everyone is writing distributed applications. WebMachine and Mochi both address a similar set of problems someone would want to address with Node. To argue that the problems people want to solve in Erlang and Node do not overlap is amazingly unimaginative.
- piotrSikora 16y agoYes, but now you're comparing WebMachine and Mochi to Node, which is fine...
- sausagefeet 16y agoSo you can imagine a project for which Node and Erlang are valid solutions? I see your argument for language vs framework, I just don't think it matters. Erlang already has a concurrency solution, and it's baked into the language. NodeJS is a solution to concurrency for a language that doesn't have one. I see comparing the two as valid because the question we are discussing how to solve the problem of performing concurrent work.
- piotrSikora 16y agoOK, let me put this differently. Why do people use Node.js? Because it solves concurrency issues or because it's easy to use JavaScript application server? Why do people use Erlang? Because it solves concurrency issues or because it's massively distributed and fault-tolerant system? Just look at the popular projects and communities behind those two projects :) Don't get me wrong, I agree that both solve concurrency issues, but this is just tiny part on which they overlap and I don't believe that they are meant to solve the same problems.