I am sorry but you do not understand what we are talking about. Do not worry, we have all been there at some point and it is on my best interest to explain to y

I am sorry but you do not understand what we are talking about. Do not worry, we have all been there at some point and it is on my best interest to explain to you what's going on :) The sentence "the bad design of node.js does not allow to manage the thread pool from outside" implies two things initially, 1. that there is a thread pool, which is part of the architecture of node.js and 2. that this thread pool cannot be managed by an external program. On the same sentence, they then try to use these concepts combined as an argument to "the bad design of node.js". What I wanted to convey is that this statement -> "the bad design of node.js" is a huge hyperbole and it is blatantly wrong, since it is actually a very good "real-world" example of good software design and practices. Anyone that has spent at least a couple days interacting with the developer community behind node.js and sister project can attest their level of knowledge, talent and commitment. Also, just bashing on a project that you're building on top of is an extremely tasteless display of vulgarity ...