Live data from Hacker News

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

github.com

271–280 of 330 posts

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

#271

Earlier quoted context omitted.

> I’m the author of this PR. > And yes, the PR description is entirely Claude. If you didn't write it, you're not the author. That's how it works, man. I would also love to read that blog post about the Rust rewrite, when you get it published.

Tell your boss I’ll do your job for 20% of your pay

[flagged]

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

#272
post #264

Earlier quoted context omitted.

[flagged]

Why do you feel so threatened that a person is ‘not impressed’ with a thing? Is it a moral fault to have doubts and concerns now? ‘Quick! Get him! We have found a skeptic ’ - sounds like a cult to me.

[flagged]

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

#273

Earlier quoted context omitted.

I think AI is fine, the problem is what you mentioned: vibe coding. Have AI do work for you, it’s certainly faster in most cases. But just know exactly what it’s generating and building before putting it into production. That’s not some massive bar to surpass.

Yeah, but you dont know who is vibe coding and who actually knows the output of what they had LLM make This leads to lack of trust, which the entire open source community is based on. Even if that vibe coded slop is flawless, the stigma will never go away.

That’s why you read the code and see what it looks like

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

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

Everyone's excited about using AI to make their quick end products. But no-one wants to actually build on or rely on vibe-coded frameworks, languages, or tools.

I am constantly confused at work that people see AI as binary: it’s either a person writing the code and taking ownership of it, or it’s AI and the poor person has no control. It’s rather bespoke or entirely vibe coded. Why? When I use AI it’s still me writing the code, I just get better autocomplete and a tool that can verify my changes using fuzzy sentence as the linting rules. Why did so many people just immediately assumed that it all must be vibe coded now? Maybe it’s because everyone hates reviewing code they didn’t write?

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

#275
post #237
post #128

Earlier quoted context omitted.

I understand that some developers produce very poor code. Maybe in some companies it's the norm. Luckily for me, I've seldom worked alongside such developers. In my company, the code Opus 4.8 is able to generate appears competent, but if you dig a bit, it contains way more timebombs than anything I've seen the team members develop.

Time bombs and just 2-3x the amount of code for the same thing. I recently rewrote a Claude generated feature from 3000 lines to 800. I guess AI fans are just predicting that no one will have to read the code in the future or something like that.

Yeah, I suspect the 2-3x amount of code, but I can't prove it yet. This will wait for the next report :)

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

#276
post #31
post #29

Eh, Firefox/Thunderbird had multi-threaded JS in SpiderMonkey in the late 90s. Then it was removed it because it made garbage-collection a real mess (the JavaScript gc needs to walk through lots of C++ data, some of it may have specific requirements for destruction/finalization). I hope it's better this time :)

The JS / interoperability is why V8 eventually added a C++ GC.

But last time I checked (which was admittedly a while ago), JavaScriptCore didn't have one, no?

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

#277

Earlier quoted context omitted.

Threads which can’t share state are called processes.

Fair-ish point, if a bit cheeky. But threads can be still threads, i.e. in the same address space, but without actually having shared state between them. And then they're still threads, not processes. You could also have stuff like message ques going between them, the cost of passing data around is small then, you don't have do leave user space to put stuff in the mq's. But can you still call it "not having shared st…

> Fair-ish point, if a bit cheeky. But threads can be still threads, i.e. in the same address space, but without actually having shared state between them. And then they're still threads, not processes.

If they don’t share state implicitly, then by all relevant features they are processes. That they share an address space is not really relevant except as an opportunity for optimisation. See BEAM.

Hell, older consumer OS used to not have memory isolation, even after multitasking was introduced.

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

#278
post #252

Putting on my tinfoil hat. Did Anthropic even buy Bun because they actually use it or was it just an excuse to lob ridiculous PRs at things with at least a little bit of credibility behind them. Their way of trying to set a precedent for accepting AI code into bigger open source projects.

The author has huge online following, and influence over developers. I don't doubt the author is genuinely interested in this, but the employer definitely is supporting this too.

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

#279
post #276
post #31

Earlier quoted context omitted.

The JS / interoperability is why V8 eventually added a C++ GC.

But last time I checked (which was admittedly a while ago), JavaScriptCore didn't have one, no?

No idea, I never used it, nor looked into its internals.

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

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

I was already not much interested into it, now even less.
Post reply on HN