Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

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

github.com

Post reply on HN
Print view View original

71–80 of 330 posts

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

#71

Post by MuffinFlavored »

Atotalnoob wrote: post #11
MuffinFlavored wrote: post #5

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

> Just stop caring about quality.

I'm not so sure this is true anymore. It may have been years ago but... can you honestly say "the Bun project was fully AI written, therefore the quality is poor"?

Any concrete examples/proof?

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

#73

Post by Waterluvian »

pizlonator wrote: post #70
hexasquid wrote: post #64

Earlier quoted context omitted.

This is consistent with the endless contempt people have had for JavaScript and those that use it.

Yeah I don’t get that either It’s a super successful language

I think with ES6 and newer things really cleaned up and now we’re left with avoidable ugly parts, of which every language has.

Before when you didn’t even have strict equality checking, for example, you were forced to know about implicit type casting.

Getting on the same page with modules also helped a lot. Typescript directly in Node is great. Look mom, no build system!! I’m just hoping one day browsers will accept TS the same way.

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

#74

Post by baq »

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.

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

#75

Post by xlii »

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.

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

#76

Post by aardvark179 »

pizlonator wrote: post #2

I knew it was possible :-) https://webkit.org/blog/7846/concurrent-javascript-it-can-wo...

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.

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

#77

Post by monkaiju »

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.

Im here with ya :)

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

#78

Post by throwrioawfo »

> 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...

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

#80

Post by mannanj »

rustystump wrote: post #28
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

It is sad. This is a new reality. No one reads code, it is agents all the way down. It has been long enough now that I can safely say AI has not sped up project delivery nor improved quality when it did ship. Is it the AI or the people using it? Idk

Humans made the AI, and their goal is profit, so there’s no AI using people: it’s humans using people.
Post reply on HN