https://www.builder.io/blog/visual-guide-to-nodejs-event-loop
I think that JS programmers like to believe that Event-Loop is a silver bullet for all IO-bound computing issues, but they are wrong. We have access to better technology and better solutions. FP is really amazing for I/O, for example: Erlang ecosystem was designed to handle high number of I/O operations. Now we have Elixir, Haskell, Ocaml and many other well developed and production ready alternatives… So… why the f#ck people are still tied to Nodejs?
Developers are struggling to do things that are already polished and ready for years. Elixir is the key to unlock all this Erlang goodness right now, let’s just use it and stop shrugging.
https://medium.com/the-node-js-collection/why-the-hell-would-you-use-node-js-4b053b94ab8e
https://developer.mozilla.org/en-US/docs/Web/JavaScript/EventLoop
https://blog.mixu.net/2011/02/01/understanding-the-node-js-event-loop/
Well, you don’t need NodeJS for it:
https://www.fpcomplete.com/blog/2016/12/concurrency-and-node/
Golang wrecked NodeJS even when single-threading >:)
https://www.toptal.com/back-end/server-side-io-performance-node-php-java-go
https://www.akitaonrails.com/2015/12/03/the-obligatory-flame-war-phoenix-vs-node-js
https://blog.lahteenmaki.net/haskell-and-non-blocking-asynchronous-io.html