There was this video I saw about this new runtime and it looks really promising, providing a massive performance leap over deno and node.js. What do you guys think? Does it have the potential to replace node and deno in the near future?

aabeni6:
There was this video I saw about this new runtime and it looks really promising, providing a massive performance leap over deno and node.js. What do you guys think? Does it have the potential to replace node and deno in the near future?

Would you switch something, when you already have a business running on node and making money, there is no cost benefit for switching as a business, unless you're one of those coders who like to switch for the sake of something new.

In Js land, not all shiny stone is a diamond.

qtguru:


Would you switch something, when you already have a business running on node and making money, there is no cost benefit for switching as a business, unless you're one of those coders who like to switch for the sake of something new.

Well no one mentioned switching now. Op just said bun looks promising and that's the truth. It has very cool features and its not just a runtime its so much more. Obviously, a business should not switch to bun now because it still has issues here and there which is very understandable for something new. It's something to keep an eye on and maybe access later on the pros and cons for that specific business.

Its something new we as developers can give a trial on our own test projects just to test out all the hype and also see the developer's experience. nothing wrong in having a discussion about it which is what the op was asking for and not for everyone to switch now.

switching wouldn't take more than 10 minutes though

qtguru:


Would you switch something, when you already have a business running on node and making money, there is no cost benefit for switching as a business, unless you're one of those coders who like to switch for the sake of something new.

Deicide:
switching wouldn't take more than 10 minutes though

Even Kotlin and Rust still have slow adoption, it's hard to jump ship unless you're talking about as a developer but as a business, that's expensive with no business value. They could just keep optimizing node

Deicide:
switching wouldn't take more than 10 minutes though

well this largely depends on the number of times you used core node features that bun doesn't have but which they have alternatives to. Also depends on how its hosted, it could take a lot more than 10 minutes.

qtguru:


Even Kotlin and Rust still have slow adoption, it's hard to jump ship unless you're talking about as a developer but as a business, that's expensive with no business value. They could just keep optimizing node

Well, switching to Rust is steeper if you don't know the language. Bun js is still very similar to NodeJS adoption will be easier because it still supports almost everything node supports but with added benefits here and there. If Bun comes of age and completely delivers on its promises there won't be any reason not to use it. When its just node but with added benefits.

Also, NodeJS has its own team that keeps optimizing it so it's not like it has been abandoned. I remember seeing one of their new updates a few weeks after Bun js was announced which made Node faster than before. So it's still actively being worked on.

jikins:


Well, switching to Rust is steeper if you don't know the language. Bun js is still very similar to NodeJS adoption will be easier because it still supports almost everything node supports but with added benefits here and there. If Bun comes of age and completely delivers on its promises there won't be any reason not to use it. When its just node but with added benefits.

Also, NodeJS has its own team that keeps optimizing it so it's not like it has been abandoned. I remember seeing one of their new updates a few weeks after Bun js was announced which made Node faster than before. So it's still actively being worked on.

That's a valid point though, Rust is a language vs Bun a runtime.