News for hackers. Stuff that matters.
Re:Bun has an open PR adding shared-memory threads to JavaSc... by tyre on Saturday June 20, 2026 @07:38PM (#48614147)
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.

Re:Bun has an open PR adding shared-memory threads to JavaSc... by afavour on Saturday June 20, 2026 @09:27PM (#48614798)
Faster I get. But easier to use?
Re:Bun has an open PR adding shared-memory threads to JavaSc... by 0x6c6f6c on Saturday June 20, 2026 @10:43PM (#48615180)
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.

Re:Bun has an open PR adding shared-memory threads to JavaSc... by afavour on Saturday June 20, 2026 @11:36PM (#48615442)
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.

Re:Bun has an open PR adding shared-memory threads to JavaSc... by egorfine on Saturday June 20, 2026 @10:05PM (#48614996)
Yeah. Take a look at the docs. So much niceties
Re:Bun has an open PR adding shared-memory threads to JavaSc... by hn_throw2025 on Sunday June 21, 2026 @05:59PM (#48623026)
...and now we also have Nub :

https://nubjs.com/blog/introducing-nub