Comment by spartanatreyu

> Will this make it more or less likely for people to use Bun vs Deno?

I'm not sure it will make much of a difference in the short term.

For those who were drawn to Bun by hype and/or some concerns around speed, they will continue to use Bun.

For me personally, I will continue to use Node for legacy projects and will continue using Deno for current projects.

I'm not interested in Bun for it's hype (since hype is fleeting). I have a reserved interested in Bun's approach to speed but I don't see it being a significant factor since most JS speed concerns come from downloading dependencies (which is a once-off operation) and terrible JS framework practices (which aren't resolved by changing engines anyway).

----------------------------

The two largest problems I see in JS are:

1. Terrible security practices

2. A lack of a standard library which pushes people into dependency hell

Deno fixes both of those problems with a proper permission model and a standard library.

----------------------------

> And now that Bun doesn't need to run a profitable cloud company will they move faster and get ahead of Deno?

I think any predictions between 1-10 years are going to be a little too chaotic. It all depends on how the AI bubble goes away.

But after 10 years, I can see runtimes switching from their current engines to one based on Boa, Kiesel or something similar.