Live data from Hacker News

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

github.com

11–20 of 330 posts

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

#11

I know a ton of people absolutely hate this level of "LLM code + LLM PR description + LLM PR review" but my boss would have an orgasm if I was able to use AI half as well in our org... :/

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

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

#12
post #10

Imagine somebody doing a drive-by on your repo and dropping a 270k loc PR expecting you to merge it. Bonus points if they can't even put in the 0.001% smidgen of effort to write why they think the PR is useful or necessary in their own words. Oh, but we don't have to imagine it, because there are people who actually do that!

The PR is against bun's fork of WebKit, not upstream.

Oh, my mistake, I thought they were doing the zig thing again.

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

#13
post #8

One of the biggest things preventing software like SQL DB's from being written in TypeScript is the lack of proper threading. I genuinely think you could write a competitively-performant multi-threaded DB in Bun + TS if you had shared-heap threads and fast atomics/locking primitives.

…but why? JS/TS does not seem like the right tool for the job?

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

#15
This is terrifying. Evidently based on prior art by Mr. Pizlo – indeed, where's the acknowledgement of that?? (edit: I missed it) – but I'm assuming that was never translated into code.

I love the idea of experimentation and innovation; I abhor the idea of it being dependent on Anthropic and their theft. I've never rooted for the Chinese labs more strongly than after seeing this.

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

#16
post #8

One of the biggest things preventing software like SQL DB's from being written in TypeScript is the lack of proper threading. I genuinely think you could write a competitively-performant multi-threaded DB in Bun + TS if you had shared-heap threads and fast atomics/locking primitives.

I honestly should print that comment and hang it on a wall.

> …competitively-performant… Care to explain competitively to what?

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

#18

This is terrifying. Evidently based on prior art by Mr. Pizlo – indeed, where's the acknowledgement of that?? (edit: I missed it) – but I'm assuming that was never translated into code. I love the idea of experimentation and innovation; I abhor the idea of it being dependent on Anthropic and their theft. I've never rooted for the Chinese labs more strongly than after seeing this.

The acknowledgement is in the PR description, section "The design, and what it's based on".

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

#19
post #18

This is terrifying. Evidently based on prior art by Mr. Pizlo – indeed, where's the acknowledgement of that?? (edit: I missed it) – but I'm assuming that was never translated into code. I love the idea of experimentation and innovation; I abhor the idea of it being dependent on Anthropic and their theft. I've never rooted for the Chinese labs more strongly than after seeing this.

The acknowledgement is in the PR description, section "The design, and what it's based on".

Thanks, fixed

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

#20
post #8

One of the biggest things preventing software like SQL DB's from being written in TypeScript is the lack of proper threading. I genuinely think you could write a competitively-performant multi-threaded DB in Bun + TS if you had shared-heap threads and fast atomics/locking primitives.

…but why? JS/TS does not seem like the right tool for the job?

It's probably what they know so not anything new should be learned.
Post reply on HN