3 ms·
The Node.js community had figured this out long before BEAM or even Elixir existed. People tried to introduce threads to Node.js but there was push-back for th
by socketcluster 7mo ago
The Node.js community had figured this out long before BEAM or even Elixir existed.
People tried to introduce threads to Node.js but there was push-back for the very reasons mentioned in this article and so we never got threads.
The JavaScript languages communities watch, nod, and go back to work.
- leoc 7mo agoYou may be thinking of some recent round of publicity for BEAM, but BEAM is a bit older than JavaScript.
- socketcluster 7mo agoHaha. I guess the BEAM people can nod down at me with contempt and I nod down at the Elixir folks.
- seanclayton 7mo agoat least you're doubling down on your ignorance!
- xtoilette 7mo agoBEAM predates node js
- pentacent_hq 7mo ago> The Node.js community had figured this out long before BEAM or even Elixir existed. Work on the BEAM started in the 1990s, over ten years before the first release of Node in 2009.
- masklinn 7mo agoAnd BEAM was the reimplementation of the Erlang runtime, the actual model is part of the language semantics which was pretty stable by the late 80s, just with a Prolog runtime way too slow for production use.
- deleted 7mo ago[deleted]
- worthless-trash 7mo agoI think the author is trying to be clever to parody what was written in tfa.
- hlieberman 7mo agoForget Node.js; _Javascript_ hadn't even been invented yet when Erlang and BEAM first debuted.
- deleted 7mo ago[deleted]