3 ms·

Holy FUD! I'm sure all the Lisp and TCL fanboys thought the same of their supposedly superior runtimes all the way to eventual irrelevance. Hubris much?

• SamReidHughes 16y ago
  Um. What he says is basically true. Node is never going to replace Erlang for the same reasons it will never replace C++. Erlang is simply different from Javascript and no amount of runtime improvement can change that.
  • gtani 16y ago
    Not sure what "replace" and "threat to erlang" means, but: for shops that already run the JVM and .NET, I think many'd be inclined to look at akka (or scala actors) and asynch workflow as available today in F# (and promised for C# 5/.NET 5). But the important thing is that erlang is no static target, development is going very strongly: read the release notes for e.g. R14A, B and B-01.Ask questions on the mailing list if you're not sure what something is, they're very friendly. (maybe someday they'll fix apache not to give out direcotry listings like this ;-> http://www.erlang.org/download/ http://www.erlang.org/download/
  • randylahey 16y ago
    Apples will never replace oranges.