Message from JavaScript discussions
October 2018
— What Dani does is another model like promise or observable, but it's focused on high granularity and stackless code
This means, the code gets fully transformed into a continuation stack, like all code was wrapped in promises
— The model behind this can be the current of nodejs
— But this would be useless, or at least, not useful as if the model behind was a full concurrent thread pool
— I mean, multiqueue approach
— More than one event loop executing js, not just one
— N:m approach, like in golang
— Each language has different implementations of concurrency
— Not all of them use the same models
— Earlang has multiqueue approach, so similar to Hertz (+napajs)
— Other languages for example rely a lot in synchronization primitives
— Others are more like freelock