Will Node.js forever be the sluggish Golang?
1–10 of 15 posts
Re: Will Node.js forever be the sluggish Golang?
#2>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...
Re: Will Node.js forever be the sluggish Golang?
#3> 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 assu…
I'm sorry the article wasn't up to your standards.
Re: Will Node.js forever be the sluggish Golang?
#4uWebsockets is an awesome project! Been following it since the start pretty much, And I'm really glad more people out there care more about performance than throwing more servers at the problem.
Keep it up alex!
Re: Will Node.js forever be the sluggish Golang?
#5For Node to be a “sluggish Golang” in the first place, it would have to be otherwise functionally equivalent to Golang, which it is not. Writing your own TCP and SSL layers is also kind of nuts if your motivation for doing so is to optimize your Node apps.
Re: Will Node.js forever be the sluggish Golang?
#6> 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 assu…
I'm sorry the article wasn't up to your standards.
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".
Re: Will Node.js forever be the sluggish Golang?
#7Earlier quoted context omitted.
I'm sorry the article wasn't up to your standards.
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".
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.
Re: Will Node.js forever be the sluggish Golang?
#8For Node to be a “sluggish Golang” in the first place, it would have to be otherwise functionally equivalent to Golang, which it is not. Writing your own TCP and SSL layers is also kind of nuts if your motivation for doing so is to optimize your Node apps.
Node.js is very popular and some companies with lots of I/O still prefer JavaScript, they have their business logic written in it.
Re: Will Node.js forever be the sluggish Golang?
#9Earlier quoted context omitted.
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".
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.
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.
Re: Will Node.js forever be the sluggish Golang?
#10For Node to be a “sluggish Golang” in the first place, it would have to be otherwise functionally equivalent to Golang, which it is not. Writing your own TCP and SSL layers is also kind of nuts if your motivation for doing so is to optimize your Node apps.
This. It's an apples to oranges comparison. People often write in Node for the speed that they can develop. Golang's current language design does not aim for development speed, although I think it's getting better/easier.
Feels similar to comparing C# to C.