|
|
|
|
|
by batista
5152 days ago
|
|
I am talking about the cultures surrounding these languages and frameworks. Node's community rejects blocking libraries. Java's does not. So what? You get tons of Java libs to use, a majority of blocking ones and lots of non blocking on one hand, or you restrict yourself to the fewer non-blocking libs of varying quality available for Node. With Java you can also turn blocking libs to non blocking with a wrapper and threads, whereas with Node.js if it's blocking you're screwing, because the js engine is single-threaded. |
|
It's trivial to offload blocking operations to other processes in node too, it's just not the preferred option.