Tech Lead/Team Lead. Senior WebDev.
Intermediate Grade on Computer Systems-
High Grade on Web Application Development-
MBA (+Marketing+HHRR).
Studied a bit of law, economics and design
Location
Spain
Education
Higher Level Education Certificate on Web Application Development
It's OK to toy around using a side project that you know it'll be thrown in the bin after a week or two.
Working on corporate, high-budget projects it doesn't seem like an option to evaluate, at least not yet.
Level of Support: not full.
Design decisions: some of them questionable to say the least.
Level of maturity: non-existent ATM.
On the other hand, synthetic benchmarks need to be picked with a grain -or a full truck- of salt.
It's possible that in real use cases bun performs worse than Node depending on the scenario and I won't be surprised by that.
It may help on changing the roadmap for Node, whether this is good or bad it's a different topic of discussion.
Tech Lead/Team Lead. Senior WebDev.
Intermediate Grade on Computer Systems-
High Grade on Web Application Development-
MBA (+Marketing+HHRR).
Studied a bit of law, economics and design
Location
Spain
Education
Higher Level Education Certificate on Web Application Development
This discussion is being driven on this post I'm not yet pronounced on it to criticise anything, as I'm waiting to digest all the information with external sources and try a couple of things on my own.
From the corporate PoV there's zero reason to jump into new trains as always has been and as always will be. On a toy project you're risking your own time, at that level you're setting at risk monies in terms of millions so... I'm not in a hurry to know all the details and my daily job certainly has challenges waiting to be solved.
At that point, and just to grasp some stuff to answer the question here, APIs that do the same than Node's but on a different way will force you to stick with Bun due to large costs of swapping back to Node (or Deno or whatever).
Built-in JSX and TS is a nonsense, we all know since the moment they got a piece of the cake that at some point in the future they will disappear (ES will eventually add anything valuable from TS in the core API, and JSX is simply one of hundreds that catch up just because it's the one used in React).
Don't get me wrong, React is my go-to choice most of the time (usually through Next JS), but I believe these meta-languages should live in it's context, outside of the RE themselves (and there are quite a few reasons for that).
At this point, with my knowledge of Bun, it's screaming TECH DEBT out loud. Saddest thing is that this looks like a try to make everyone -using the mainstream- happy while appealing to tribal people, which is a great effort dedicated here instead on other stuff.
I just want to point out that this is a really solid and practical comment in re: to any new technology. I think there’s a little bit of a hype problem in the dev world that doesn’t match up with the corporate reality most of us in tech roles face. Change is difficult, expensive and risky.
That said, progress is great. Challenging the status quo is great, keeping up on trends is great and necessary. But I’ve seen so many new things come and go, and I know how many devs out there are trying to bring in readers or capture an audience these days, I have to take all the “BUN IS THE NEW NODE” articles with a big grain of salt.
Even if it is here to stay, it will take a long time for the corporate world to follow suit (but that shouldn’t discourage anyone from trying it out and I’m certainly enjoying the posts and discussion around it).
Tech Lead/Team Lead. Senior WebDev.
Intermediate Grade on Computer Systems-
High Grade on Web Application Development-
MBA (+Marketing+HHRR).
Studied a bit of law, economics and design
Location
Spain
Education
Higher Level Education Certificate on Web Application Development
I'm skeptical for now.
It's OK to toy around using a side project that you know it'll be thrown in the bin after a week or two.
Working on corporate, high-budget projects it doesn't seem like an option to evaluate, at least not yet.
On the other hand, synthetic benchmarks need to be picked with a grain -or a full truck- of salt.
It's possible that in real use cases bun performs worse than Node depending on the scenario and I won't be surprised by that.
It may help on changing the roadmap for Node, whether this is good or bad it's a different topic of discussion.
Out of interest, which decisions do you think are questionable?
This discussion is being driven on this post I'm not yet pronounced on it to criticise anything, as I'm waiting to digest all the information with external sources and try a couple of things on my own.
From the corporate PoV there's zero reason to jump into new trains as always has been and as always will be. On a toy project you're risking your own time, at that level you're setting at risk monies in terms of millions so... I'm not in a hurry to know all the details and my daily job certainly has challenges waiting to be solved.
At that point, and just to grasp some stuff to answer the question here, APIs that do the same than Node's but on a different way will force you to stick with Bun due to large costs of swapping back to Node (or Deno or whatever).
Built-in JSX and TS is a nonsense, we all know since the moment they got a piece of the cake that at some point in the future they will disappear (ES will eventually add anything valuable from TS in the core API, and JSX is simply one of hundreds that catch up just because it's the one used in React).
Don't get me wrong, React is my go-to choice most of the time (usually through Next JS), but I believe these meta-languages should live in it's context, outside of the RE themselves (and there are quite a few reasons for that).
At this point, with my knowledge of Bun, it's screaming TECH DEBT out loud. Saddest thing is that this looks like a try to make everyone -using the mainstream- happy while appealing to tribal people, which is a great effort dedicated here instead on other stuff.
I just want to point out that this is a really solid and practical comment in re: to any new technology. I think there’s a little bit of a hype problem in the dev world that doesn’t match up with the corporate reality most of us in tech roles face. Change is difficult, expensive and risky.
That said, progress is great. Challenging the status quo is great, keeping up on trends is great and necessary. But I’ve seen so many new things come and go, and I know how many devs out there are trying to bring in readers or capture an audience these days, I have to take all the “BUN IS THE NEW NODE” articles with a big grain of salt.
Even if it is here to stay, it will take a long time for the corporate world to follow suit (but that shouldn’t discourage anyone from trying it out and I’m certainly enjoying the posts and discussion around it).
Absolutely!