[erlang-questions] node.js vs erlang
Ivan Carmenates García
Wed Jun 18 07:49:13 CEST 2014
Hi all, Joe,
Now imagine the turn of programming technics if all browser companies could include interpretation for Erlang natively? And you could communicate two Erlang's nodes one in the client (browser) another in the server as the same way as Erlang always do, Even so without having that big community, I'm sure the entire web community will be forced to see that new tec that is in all browsers and have the same counterpart in the server
De: erlang-questions-bounces@REDACTED [mailto:erlang-questions-bounces@REDACTED] En nombre de Miles Fidelman
Enviado el: martes, 17 de junio de 2014 10:26 p.m.
Asunto: Re: [erlang-questions] node.js vs erlang
Raoul Duke wrote:
>> Let's not forget what node.js is, and it's intent: It's an
> hrm, i do not believe that statement is correct. something like Rhino
> would more fit that statement, i think. or even just V8. node = V8 +
> more stuff, so i think that sorta disproves what you wrote?
A couple of references from http://nodejs.org/about/ - both 'intro to node.js' type slide decks from Ryan Dahl - who is kind of the ultimate authority, in that he's the author of node:
A slightly earlier version
(http://s3.amazonaws.com/four.livejournal/20091117/jsconf.pdf) says this (again, slide 2):
Built on Google’s V8
Evented, non-blocking I/O. Similar to
EventMachine or Twisted.
CommonJS module system.
8000 lines of C/C++, 2000 lines of
In theory, there is no difference between theory and practice.
In practice, there is. .... Yogi Berra
erlang-questions mailing list
More information about the erlang-questions