Node.js is still way faster than Deno

Newly released Deno 1.9 promises “Rust-like” performance, still outrun by Node.js

There is no incentive swapping to Deno, especially not from Node.js. Node.js has history and is not exactly a performance beast on its own, but it does have strong support for native add-ons. These can seamlessly augment and boost Node.js to heights way above what is possible with Deno.

Q&A

  • “you aren’t using WebSockets specifically but instead using the uWebSocket.js library which also supports HTTP (that could really use some clarification).”
    Right, “uWebSockets.js” is a library doing both HTTP and WebSockets. This comparative test is on HTTP, since HTTP performance is what Deno 1.9 boasts about.
  • “You are such a bad reader” […] “performance boost that Deno got this release is happening ONLY in HTTP” […] “you are comparing WebSocket implementations”
    I am comparing HTTP. Irony.
  • “It’s hilarious how you’re comparing a _native_ impl to one written in Javascript, and the native one _only_ performs twice as fast as Deno’s JS impl”
    Deno 1.9 uses a native Rust-written HTTP server called “Hyper”, not a scripted one. That’s the whole point of this post.
  • “I have found my way into a fanboy vs fanboy fight”
    Node.js is a piece of garbage platform. But that doesn’t mean I cannot perform scientific tests involving it.
  • “Are you a 12 year old sufferer of ADHD with too much free time and a trickle of mom & dad’s money to keep you out of their hair, or something? You write — and then copy responses back into the edited body of your post — like old people fuck.”
    Correctamente.