4 ms·

By that logic, anything that abstracts parallelism away is "human". Actors are human. akka.io is human. Erlang is "human"... but the latter two are actually som

by th0br0 13y ago

By that logic, anything that abstracts parallelism away is "human". Actors are human. akka.io is human. Erlang is "human"... but the latter two are actually some weird meta-human because they provide true parallelism. One could as well propose a counter-theory: Node.js is _not_ (or rather anti-) human, because it takes away the joy of solving complex parallelism-related issues and thus limits a human's intellectual development. (Oh and your last word contains a typo: "excersize")

michaelsbradley 13y ago
JavaScript's (and so Node's) limited concurrency primitives and unfettered mutability have, in my experience, resulted in its making a number of concurrency-related problems harder to deal with, not easier. Mutability can be tamed with the help of libraries that provide immutable collections[1]. The best concurrency facility for JavaScript that I've found is core.async[2], but you can't really mimic it with vanilla JavaScript as the language doesn't provide macros. It might be interesting, though, to see if the core.async patterns could be implemented in terms of sweet.js[3] and with the help of esprima or acorn[4]. [1] mori, for example: http://swannodette.github.io/mori/ http://swannodette.github.io/mori/ [2] https://github.com/clojure/core.async https://github.com/clojure/core.async [3] http://sweetjs.org/ http://sweetjs.org/ [4] http://esprima.org/ http://esprima.org/ [&] http://marijnhaverbeke.nl/acorn/ http://marijnhaverbeke.nl/acorn/
igravious 13y ago
typos: excreeting, benifit (singular), disatisfaction, concurency, transfering, asyncronous (in an article about parallelism, oops!), everytime, asyncronous (again), benifits (plural), philisophically, asyncronous (yet again), and finally excersize
- jondavidjohn 13y ago
  yay, thanks for the spellcheck... I'll make sure to do that next time.
_random_ 13y ago
I think he means that "to err is human". It is very easy to make frustrating mistakes in JavaScript which is not just dynamic, but even weakly-typed. Following that Node.js is obviously most human.

by th0br0 13y ago

michaelsbradley 13y ago

JavaScript's (and so Node's) limited concurrency primitives and unfettered mutability have, in my experience, resulted in its making a number of concurrency-related problems harder to deal with, not easier. Mutability can be tamed with the help of libraries that provide immutable collections[1]. The best concurrency facility for JavaScript that I've found is core.async[2], but you can't really mimic it with vanilla JavaScript as the language doesn't provide macros. It might be interesting, though, to see if the core.async patterns could be implemented in terms of sweet.js[3] and with the help of esprima or acorn[4]. [1] mori, for example: http://swannodette.github.io/mori/ http://swannodette.github.io/mori/ [2] https://github.com/clojure/core.async https://github.com/clojure/core.async [3] http://sweetjs.org/ http://sweetjs.org/ [4] http://esprima.org/ http://esprima.org/ [&] http://marijnhaverbeke.nl/acorn/ http://marijnhaverbeke.nl/acorn/

igravious 13y ago

typos: excreeting, benifit (singular), disatisfaction, concurency, transfering, asyncronous (in an article about parallelism, oops!), everytime, asyncronous (again), benifits (plural), philisophically, asyncronous (yet again), and finally excersize

jondavidjohn 13y ago
yay, thanks for the spellcheck... I'll make sure to do that next time.

_random_ 13y ago

I think he means that "to err is human". It is very easy to make frustrating mistakes in JavaScript which is not just dynamic, but even weakly-typed. Following that Node.js is obviously most human.