golanghacker4

3 ms·

1. 1.▲
   by golanghacker4 11y ago

   No, I think the author genuinely views Node.js/NIO as a bad performance/readability trade-off that was over-hyped and inferior to other existing platforms.
2. 2.▲
   by golanghacker4 11y ago

   I don't think they are. Other than the first paragraph, with its self-deprecation and references to Node.js and NoSQL, which seems intended to head-off the derision such a hipsterish manifesto would rightly incur, the rest seems entire
3. 3.▲
   by golanghacker4 11y ago

   "Oh yes indeed. Just as Node.js and NIO proved to the world that bare-metal performance is always worth the consequent unreadable code" Node.js is hardly bare metal and non-blocking IO is hardly new; Unix programmers have been wri