Deno 2 was a major release entirely about shoring up Node compatibility. That's arguably a big reason for why Bun seems to have a higher velocity right now of t

Deno 2 was a major release entirely about shoring up Node compatibility. That's arguably a big reason for why Bun seems to have a higher velocity right now of the trio. Deno put in a ton of engineering into Node/npm compatibility, it shows, and right now I would recommend trying Deno as having suprisingly few compatibility/ecosystem issues remaining. (Deno has not stayed entirely still, other new features were added outside of that compatibility effort, but Bun doesn't have Node compatibility as much as a goal today and so gets the fast mover award.) I started using Deno in hobby projects because I like the out-of-the-box defaults a lot better than Node (deno.json is a lot simpler than a lot of the cruft that package.json has acquired, but also includes more things in one place like out of the box eslint support [deno lint] and prettier-equivalent [deno fmt]). Also, Deno Deploy has a generous free tier and that's a healthy incentive for hobby projects that want a modest database (Deno KV) and basic task processing queues.