On: Bun has an open PR adding shared-memory threads to JavaScriptCore

[afavour]

I’m amazed folks ever migrated to it at a workplace level TBH. It’s a VC funded runtime, something was always going to happen to it. Node is boring but its governance and ownership is clear.

[tyre → afavour]

Well, it was (is?) significantly easier to use, faster, the team behind it is fantastic, and generally had enough compatibility to run the projects I needed it to.

When it’s enough of a drop-in replacement, that’s more than good enough. As long as we’re not adding a hundred bun-specific things, it’s not terribly difficult to back out of, either. Kind of a no-brainer.

[afavour → tyre]

Faster I get. But easier to use?

[0x6c6f6c → afavour]

There is no comparison when running a TypeScript project with Bun vs with Node. Or when mixing ESM and CJS. Or when setting up unit testing.

Node and its ecosystem was considerably behind in multiple regards.

[afavour → 0x6c6f6c]

OP said:

> it’s not terribly difficult to back out of, either

Things like ESM/CJS interop are great but backing out of an ecosystem that uses it is absolutely not trivial.

Either it’s a trivial replacement you can drop in with no changes or it’s a notable change you can’t easily switch out. It’s not both.

[egorfine → afavour]

Yeah. Take a look at the docs. So much niceties