Ask HN: What can't Deno do that Node can
I've run a couple web servers for years with nodejs. I'm thinking of using Deno instead for a new project and wondering what Deno can't do. I use Postgres, Cors. Nothing really tricky, but just wondering if anyone has tried this and has experience arguing against this choice.
8 comments
The big factor is going to be library support. Deno is younger and doesn't have the same ecosystem. You can do all the same stuff, but in node, someone may have figured out the hard part for you.
Node is awesome and very mature. I can literally make any backend ready in a day with basic setup that takes days in any other framework
I encourage people to switch to node because even a frontend developer understands typescript and java script
Deno can replace node but then there will be bun and in all that race I think Node will still be champ
I encourage people to switch to node because even a frontend developer understands typescript and java script
Deno can replace node but then there will be bun and in all that race I think Node will still be champ
I've been prototyping with Supabase recently and they use Deno for their functions. It's been a pain tbh, maybe I'm just too new to it (maybe it's Maybelline) but it's basically just a big, unnecessary abstraction imo.
I guess something like sandbox computation, where you can execute arbitrary code on the fly (within a sandbox environment).
require('dependency')
Can you elaborate? I am guessing you mean you can’t do dynamic imports?
Render React components without weird hanging bugs and stuff like that. At least I was never able to get it to. And whichever DOM implementation you pick will either be early and lacking features, or not intended to work with Deno.
My use case was automated testing of React components. All stuff I’ve done a million times with Node, nothing crazy.
My use case was automated testing of React components. All stuff I’ve done a million times with Node, nothing crazy.