4 ms·

I hope this is good marketing for Deno and not just a huge distraction. I feel like Bun is running circles around them right now. I feel like there might even b

I hope this is good marketing for Deno and not just a huge distraction. I feel like Bun is running circles around them right now. I feel like there might even be room for 3 winners (Bun, Deno, Node) but I don't understand the point of this. If Deno wins this battle will that make we want use Deno more?

bsimpson 2y ago
I think it's a passion project for the founder, who built his career on JS and is offended that Oracle (a company famous for deploying lawyers instead of technological expertise) claims to control it.
- krashidov 2y ago
  I think it's a little more than a passion project since it's posted on the official deno blog. I don't think it's a net negative of a pursuit, but I follow the founder of bun on twitter and he just keeps shipping shit whereas the most I hear from Deno is this lawsuit. I'm not saying Deno doesn't have merits, I just wonder if this is the thing they should be focused on
  - crabmusket 2y ago
    > the most I hear from Deno is this lawsui Two days ago: https://deno.com/blog/jsr-open-governance-board https://deno.com/blog/jsr-open-governance-board Maybe don't trust your Twitter feed to be a balanced information diet. But yes, Bun's current strategy is "churn out code" whereas Deno has a different pace and approach. They're trying to build different things, and have a lot less catch-up to play than Bun.
    - deleted 2y ago
      [deleted]
    - krashidov 2y ago
      > But yes, Bun's current strategy is "churn out code" whereas Deno has a different pace and approach. They're trying to build different things, and have a lot less catch-up to play than Bun. Are they trying to build different things? I feel like they're direct competitors. Are you a Deno user? Curious what your experience has been
      - crabmusket 2y ago
        Well e.g. JSR is different to anything I've seen from the Bun team, so yes. I didn't mean Deno and Bun's core offerings are different, but that there are differences in what they're each applying time and effort to. I'm a Node user. I haven't yet seen a compelling reason to switch that justifies potential compatibility/ecosystem issues.
        WorldMaker 2y ago
        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.
        crabmusket 2y ago
        I also used Deno for some side projects before 1.0 and I really like it. Especially its focus on web stanrards, and yes, being an all-in-one tool. But I don't have the time or inclination for a lot of side projects these days. I actually feel much more warmly to Deno than Bun, and would use it if I felt like it made sense. I tried to avoid advocating either way in my former posts in this thread. But regardless of my personal feelings, at work pragmatism rules the day.

bsimpson 2y ago

I think it's a passion project for the founder, who built his career on JS and is offended that Oracle (a company famous for deploying lawyers instead of technological expertise) claims to control it.

krashidov 2y ago
I think it's a little more than a passion project since it's posted on the official deno blog. I don't think it's a net negative of a pursuit, but I follow the founder of bun on twitter and he just keeps shipping shit whereas the most I hear from Deno is this lawsuit. I'm not saying Deno doesn't have merits, I just wonder if this is the thing they should be focused on
- crabmusket 2y ago
  > the most I hear from Deno is this lawsui Two days ago: https://deno.com/blog/jsr-open-governance-board https://deno.com/blog/jsr-open-governance-board Maybe don't trust your Twitter feed to be a balanced information diet. But yes, Bun's current strategy is "churn out code" whereas Deno has a different pace and approach. They're trying to build different things, and have a lot less catch-up to play than Bun.
  - deleted 2y ago
    [deleted]
  - krashidov 2y ago
    > But yes, Bun's current strategy is "churn out code" whereas Deno has a different pace and approach. They're trying to build different things, and have a lot less catch-up to play than Bun. Are they trying to build different things? I feel like they're direct competitors. Are you a Deno user? Curious what your experience has been
    - crabmusket 2y ago
      Well e.g. JSR is different to anything I've seen from the Bun team, so yes. I didn't mean Deno and Bun's core offerings are different, but that there are differences in what they're each applying time and effort to. I'm a Node user. I haven't yet seen a compelling reason to switch that justifies potential compatibility/ecosystem issues.
      - WorldMaker 2y ago
        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.
        crabmusket 2y ago
        I also used Deno for some side projects before 1.0 and I really like it. Especially its focus on web stanrards, and yes, being an all-in-one tool. But I don't have the time or inclination for a lot of side projects these days. I actually feel much more warmly to Deno than Bun, and would use it if I felt like it made sense. I tried to avoid advocating either way in my former posts in this thread. But regardless of my personal feelings, at work pragmatism rules the day.