Hey there, fellow developers! π₯οΈ
Well, when it comes to web development, YOU'RE RIGHT! There are just so many tools! But the most popular option ...
Some comments have been hidden by the post's author - find out more
For further actions, you may consider blocking this person and/or reporting abuse
Hey, thank you for the fantastic article. I appreciate the insights shared.
I'd like to share my experience with
Bun. While it's incredibly fast and has great features for real-world applications, I encountered several unfixed bugs when using it withsqlite3.Some of these bugs that were working in previous versions. I believe it's best to use
Bunfor minimal scripts due to easier debugging and fixing.As the ecosystem matures, using
Bunover node.js makes more sense to me.Ohh! Well yeah I think bun is relatively very new and needs much improvement that is why organisations still use node.
If performance were really the most important metric, JavaScript would not even be considered. Bun is an experimental runtime written in an experimental language. I think it is too bleeding edge for production right now.
Thatβs an interesting point because before bun even started the performance metric I donβt think people even talked about it as there wasnβt much to compare with.
At the time Node was created, there was a lot of talk about performance - but this was down to the fact that most other server architectures were doing thread-based serving - effectively synchronous serving but on a thread. Turns out that the async / event loop approach was way more scalable for traffic that wasn't doing heavy calculations. These days you have the same principle in lots of other architectures and so those turn out to be more performant than JS in some circumstances.
Bun looks promising, but Node provides performances that most people don't even reach. Take a look at Restana handling 79000 req/s:
github.com/BackendStack21/restana
Exactly Bun aims more towards simplicity and speed but Node is like the superpower with strength and capabilities.
it is very interesting but i think node is better because i never used bun ....if you used then can you tell what is it
I believe it all comes down to your requirements but yeah Nodejs is like evergreen.
yes node is very exited ...if you know then can you tell about Bun
I would suggest you to go through the Bunβs official platform to get a better idea as it is kind of difficult to share everything over here.
Ok.. thanks for supporting β₯οΈ
Anytime.
interesting read
Thank you! Glad to hear it.
Bun seems fast, but Node.js is king in any other relevant metric. It's far more likely that Node.js will evolve and get faster instead of Bun getting traction. At least for me.
Yes absolutely!
If Bun can slove the pain points of Node, rather than just the performance, I'm sure it'll slowly get a higher share. on the contracry, nodejs is not really more of a performance issue right (web development)?. I think that more performance-orientaed scenarios will not consider nodejs.
Absolutely! Good point
Just be careful, Bun isn't yet ready in all aspects. For example, all crypto functions (such as hashing, AES, etc) is around 10x slower than Node.js at the moment.
Yes absolutely that is why I referred it as a new child.
Node
Choosing the one that stood the test of time
Great Choice! My own preference π
Bruh.. Your bun code is wrong.. it doesnt even run
Thanks for pointing it out, but I believe this typescript error might get resolved if you run it from your shell.
Although this has been highlighted on Bunβs QuickStart guide.
Please try this code:
const server = Bun.serve({
port: 3000,
fetch(req) {
return new Response("Bun!");
},
});
console.log(
Listening on http://localhost:${server.port} ...);Hope this works for you.
bun version 1.1.1
I have shared another code, please try it and let me know if you still face some errors, please share it with me and I would also like you to go through the QuickStart guide on official website.
Larger scale projects can still benefit from Bun locally or in continuous integration pipelines. Running tests faster and better local package management save time in the development life cycle.
Yes absolutely, but bun is also new and lacks in few things although the newer version sounds much more promising.
Great post! π keep it up! π
Thank you so much!
Clickbait article.
Value your opinion!
I'm using bun in development and it's fantastic saves a lot of time
What about Hono, which can be used in both nodejs and bun runtimes?
As far as I have heard it works better with bun but havenβt really tried it so canβt say for sure.
ππΌ
Thank you!
Switched to Bun recently - the performance is incredible.
Yes itβs really fast.
Nice article, thanks for sharing it!
Glad to hear!
I've been using Bun for the last few days and it's really fast.
I tested both of them and bun is faster then node or Deno.
Yes! Bun is faster but it is not yet designed to build large scale complex applications unlike node.
Iβve played with Bun before and it looks really promising. Thanks for the post!
nice article!!
Thanks for sharing
Glad to hear!
Interesting!
Thank you!
Unfortunately, Bun in not supported on a lot of cloud and PaaS providers. It's a bit of a catch22, but once more cloud providers support Bun then I could see it getting more wide use adoption.
simple solution: run on both.
Great π
Id wait till serious companies with serious money start using it :)
But donβt you think then again the situation of too much competition will be created and might lack behind if we start learning it late like happening with MERN stack.
This is such an interesting read!! Waiting for more such reads keep it up!!
Thank you so much!!!!
Hi, thank you for the great article.
Glad to hear!
It's YAJF! Yet Another JavaScript Framework
Why should you use it?
Because it's 10 minutes newer than the previous YAJF. π€
Who Will Use It?
New-new-devs who don't know about (or haven't tried) previous YAJFs.
They'll tout it as the greatest thing ever -- because they don't know about previous things ever.
π€
Am I funny yet? π
I don't get it... this is a day 1 comparison article in, ... 2024?
No sir, this actually is a comparison of what you can choose in 2024, based on data till the date this article was published, if that was your doubt.
This article is littered with errors, not least of which is this:
It is not built on Node, it's built from scratch with Zig.