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

Post by sergiotapia » Sat, Jun 20, 2026, 8:42 PM UTC

xlii wrote: post #75

I wonder if I'm the only one for whom the bun project vanished completely. In software code is only part of the package. Stability and trust are big part of it, too. And for me 1800 files change PRs created by Anthropic overseen by one person is not necessarily adding to the package. Even it that'd be the best code and design in the world, I won't use it. I don't trust it.

Post by MuffinFlavored » Sat, Jun 20, 2026, 8:49 PM UTC

Yoric wrote: post #36

Atotalnoob wrote: post #11

Earlier quoted context omitted.

Just stop caring about quality. It makes it 10x easier to produce slop with AI if you never bother to check

I just wrote an internal report in my company. My conclusion from the project I'm working on is that, as of this day, there is no way to have both this so-called 20x performance improvement _and_ any kind of quality. Or security if whoever is running the agent has any token in an .env anywhere on the same file system. We'll see in which direction the CTO takes this. My bet is not on quality.

Post by nasretdinov » Sat, Jun 20, 2026, 8:54 PM UTC

baq wrote: post #74

nasretdinov wrote: post #21

The code needs to be not in the state of "no obvious bugs", but "obviously no bugs". Especially the programming language runtime. Otherwise there is no hope you can sustain any development whatsoever

Won’t happen unless the thing is implemented in lean4.

Post by pizlonator » Sat, Jun 20, 2026, 8:54 PM UTC

sroussey wrote: post #94

aardvark179 wrote: post #76

Earlier quoted context omitted.

It’s certainly possible, but I worry that weird things can happen when doing something as “simple” as defining a property if another thread is messing with the prototype chain. Even thread safe property maps can’t entirely save you because operations that need to go up the prototype chain are not and cannot be atomic.

This won’t work well without a few other things, like structs https://tc39.es/proposal-structs/

Post by Me1000 » Sat, Jun 20, 2026, 8:59 PM UTC

user43928 wrote: post #85

throwrioawfo wrote: post #78

> Shared-memory threads for JavaScriptCore. new Thread(fn) runs fn on another thread, in the same heap, with the same objects. No structured clone, no message passing, no SharedArrayBuffer-only escape hatch. You share an object by sharing the object. If you can't even be bothered to write a non-slop PR description, it doesn't bode particularly well for the content of the PR itself...

I previously gave this author and the bun rewrite the benefit of the doubt. But an obvious slop PR to the WebKit repository? I'd tap out here too if I was a maintainer. Even if the change was perfect, if you could not be bothered to write the PR description, I am not going to waste my time with it. Edit: My bad, the PR is to a fork, in that case it's not our business how the PR description is written.