><i>It is productive and elegant, sure, but lacks in performance. Emerging are projects like Fastify, and hundreds alike. They all aim to provide what Express does, at a lower performance penalty. But that’s exactly what they are; a penalty. Not an improvement. They’re still strictly limited to what Node.js can provide, and that’s not much as compared to the competition</i><p>The whole article is badly written.<p>First it assumes that the lower performance is something insufferable -- when in most cases, and for most project, it doesn't matter at all.<p>Then it fails to understand the important of developer pool, convenience, ecosystem, etc, as if JS and Node could be willy nilly replaced by Golang for every project.<p>Third, it pisses (as above) on Node web framework projects, just because Node.js has a performance top (as a single process lower than Golang.<p>Also the importance of the overall architecture for performance is not accounted at all -- or the fact that as long as you add some database queries the speed benefit over Node diminishes...