3 ms·

I am not sure if either fast or convenient applies here. Maybe I have different definitions.

• kamranjon 3y ago
  I think they mention fast because the built-in Deno webserver is now faster than node:http. I've been following Deno for a while, and even deployed a service with it, and it's awesome that it has finally surpassed node performance. I think if you've used Deno before convenient definitely fits, you can build quite a bit without needing external libraries, typescript by default, you kinda just start working on your problem - just a much cleaner version of what node could have been in my experience.
  • porsager 3y ago
    Just use uWebSockets.js[1] in node, and you'll leave Deno in the dust again. (uws is also what's under the hood in bun) https://github.com/uNetworking/uWebSockets.js https://github.com/uNetworking/uWebSockets.js
    • mmastrac 3y ago
      The fastwebsockets library one of our team developed gives uWebSockets a run for its money under a lot of circumstances (though we trade performance improvements and the top spot back and forth). We're constantly working on improving the performance of Deno from top to bottom and it's a marathon. We don't want to be fastest at the expense of security or maintainability and the results from the last couple of months have been pretty awesome. I can't necessarily speak for priorities at any point in time, but I can say that performance is very important and literally what I'm working on most of the time.