You must log in or register to comment.
No matter how low overhead you get, it’s still node, which means it’s still an actual order of magnitude behind Go & Asp.Net Core (~600k RPS raw Node, ~7mill RPS with asp.net core & go). Which means 10x the compute costs for the same outcomes.
It’s not a bad thing, to be clear, but the underlying technology has issues that frameworks on top of it can’t really address.
Also the meme of “yet-another-framework”, which may or may not be in some state of deprecation, abandonment, or incompatibility in 5 years.
No matter how low overhead you get, it’s still node, which means it’s still an actual order of magnitude behind Go & Asp.Net Core
I’m not so sure about that, at least in general terms. Some benchmarks show Node.js outperforming Go. See Web server ‘hello world’ benchmark : Go vs Node.js vs Nim vs Bun (previous discussion here)
