Subscribe
Sign in

The decision fatigue is killing me

Laurentiu Ciobanu
34 replies
There's a lot of buzz around new runtimes for JS on the server (Bun is making serious waves). Should I stay with Node, should I switch to Deno? Can Bun even be considered for production use? Are the extra features of Bun worth switching? (I also wrote a bit about a feature of Bun that is not so well-known: https://blog.ciobanu.dev/posts/bun-macros). So, out of curiosity, what tool do you plan to use to run your server-side JavaScript for your next project?

Replies

Savian Boroanca
I think Node is good enough for most of the projects. Prove me wrong! 👇
Vasi M
Sessions
@savian_boroanca uhm.... where do I begin?
Mirel Bițoi
@savian_boroanca I feel the same. It gets the job done.
Savian Boroanca
@vasi_m start small and then expand. I might agree with you, on some points.
Iscu Andrei
@savian_boroanca @ochanissi That's the problem... It just gets it done... But Bun can offer things that would make it more efficient. A simple car like a Dacia can get the job done. But it ain't exactly a Ferrari =]
Adrian Steriopol
Thanks for the post. A lot of useful info 🙌
Octavian Codrea
I guess you have to consider the scale of the project first. You might win in the long term if you spend some time to research alternatives to Node in the initial phase, and decide on something else that may be more suitable to what you need.
Alexandru Frentescu
Good question to debate
Iscu Andrei
While I'll use Node for work projects, I'm actually trying out Bun at the moment and will keep an eye on it.
Savian Boroanca
@iscu_andrei huh, you are a Node user and voted for Bun. Why?
Vasi M
Sessions
@iscu_andrei you going down the rabbit hole....fast
Laurentiu Ciobanu
@iscu_andrei I also think bun is going somewhere. Oven (the company that makes Bun) just got a 7m investment to push bun forward.
Iscu Andrei
@savian_boroanca cause NodeJS is well established and stable. But Bun has huge potential and while "fresh" on the scene, may come to overtake Node in functionality in time.
Cristian Toba
Node is the way to go for full-featured apps and Deno is the best in class for small apps or serverless.
Laurentiu Ciobanu
@ictoba I think node can also do pretty good on the serverless side. Deno deploy and cloudflare workers use v8's isolates to run your code instead of containers. That's what makes them fast, but you could use the same tech in Node, as it's powered by v8 as well and has access to the isolates. This package wraps it up nicely https://github.com/laverdet/isol...
Mirel Bițoi
Node is what I use on most of my projects and I'm the most comfortable with. Looked in Deno and it's pretty cool, but haven't had the chance to work with it yet. I'll look in Bun as well.
Adriana Virlan
I am also curious in finding out the differences about these two beautiful apps. I am thinking Node is a bit better, but it's interesting to see so many points of view on this topic.
Adriana Virlan
@laurentiu_ciobanu @iscu_andrei @ictoba @vasi_m @savian_boroanca I think so. It reminds me of Shakespeare "To be or not to be".
Iscu Andrei
@savian_boroanca you can't call 'em kittens, now can you? =]
Johnny Alex
It comes to what you need (not want) most in the end. Sure, you can go safe and boring but what about risky and fun ? Joking aside, if you tried out all of them and have an idea of where they fit best, go and apply that in your use case. It depends on what your priorities are and what you're trying to achieve.
Codrut Rotaru
First time hearing about Node alternatives, sounds exciting! Thanks for the post.