[coldtea]

>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

The whole article is badly written.

First it assumes that the lower performance is something insufferable -- when in most cases, and for most project, it doesn't matter at all.

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.

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.

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...

[alexhultman]

I'm sorry the article wasn't up to your standards.

[coldtea]

It's mostly the overall tone hammered on, e.g. starting with: "Will Node.js forever be the sluggish Golang?" which is click-baity.

In fact I gave up around the insults at various Express-successors, and missed that the main point of the article is the µWebSockets.js.

Why not go into that directly and skip the rest? That's what people would want to know, not that "Node is worse than Golang in raw performance".

[alexhultman]

I thought you said you had assessed the _whole_ article as bad? You didn't read past the ingress, the motivation of the work done.

[craftinator]

He obviously went and reviewed the rest, or how would he know about the uWebsockets portion? His point is that the article is poorly written enough that he had no desire to finish it, and I fully agree. More information and less disparaging fluff would make this piece much more attractive to the engineers of the world.

[coldtea]

I stopped around the graph ("No so called “web framework” for Node.js, whether Fastify or not, can surpass the red line").

It didn't seem to point to some novel work, just to be some kind of piss take on Node.