[fg137]

Very interesting, but without an ecosystem I doubt this person can keep maintaining it long term. Bun users who don't care about slop will continue to use Bun, those who care will go back to Node.js, and there isn't much left for this project. It is a gigantic task to maintain a JS runtime and add features.

[ForHackernews]

What's the situation with Deno these days? I care about having a fast/secure/modern JS environment and I've been burned by node.js in the past.

I'm not that optimistic for Bun with all the recent churn/slopcoding but the pitch of "use this one good TS tool for everything" is appealing.

[fg137]

Deno doesn't seem to have as much momentum ever since Bun showed up, and there is concern about the status of the company. I doubt anyone wants to rely on Deno at this time.

Node.js has come a long way, and its support for TS is fairly good these days. Of course it's not an "all-in-one" experience, but I really don't know if it matters. Setting up a bundler is easier than ever, and for complex/niche use cases, you'll likely need webpack instead of whatever comes with Bun. Let alone all the other options that take care of the entire build toolchain.

Choosing a runtime just for the tools it brings isn't as good a decision it seems.

[epolanski]

What if adding features wasn't the scope and just providing a fast and memory efficient runtime that doesn't pretend to be everything at once.

[fg137]

People will move to a different runtime that provides the features they need.

[andsoitis]

> Bun users who don't care about slop will continue to use Bun

What slop does Bun create or cause?

[adithyassekhar]

Bun is the slop

[skeledrew]

Seems to be good slop, since Claude Code works so well.

[andsoitis]

Why do you say Bun is the slop? Does it lack utility?

[JackSlateur]

(without having the answer from GP): your two questions are fully unrelated: first is about long term, second is about only "now".

To try a metaphor: "Why would you grow crops ? Do you lack food on your table ?"