News for hackers. Stuff that matters.
Re:Bun has an open PR adding shared-memory threads to JavaSc... by adamddev1 on Saturday June 20, 2026 @06:44PM (#48613683)
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.
Re:Bun has an open PR adding shared-memory threads to JavaSc... by maddmann on Saturday June 20, 2026 @08:53PM (#48614616)
What about Claude code?
Re:Bun has an open PR adding shared-memory threads to JavaSc... by deaddodo on Saturday June 20, 2026 @09:18PM (#48614756)
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.

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

Re:Bun has an open PR adding shared-memory threads to JavaSc... by ok_dad on Sunday June 21, 2026 @05:35AM (#48617226)
That’s why you read the code and see what it looks like
Re:Bun has an open PR adding shared-memory threads to JavaSc... by LikesPwsh on Sunday June 21, 2026 @08:40AM (#48618423)
In the infamous words of Spolsky - "It’s harder to read code than to write it."
Re:Bun has an open PR adding shared-memory threads to JavaSc... by llbbdd on Sunday June 21, 2026 @12:17AM (#48615636)
What is vibe coding?
Re:Bun has an open PR adding shared-memory threads to JavaSc... by OuterVale on Sunday June 21, 2026 @01:58AM (#48616064)
The term was coined by Andrej Karpathy in early 2025 where he wrote:

> There’s a new kind of coding I call “vibe coding”, where you fully give in to the vibes, embrace exponentials, and forget that the code even exists. […] I ask for the dumbest things like “decrease the padding on the sidebar by half” because I’m too lazy to find it. I “Accept All” always, I don’t read the diffs anymore. When I get error messages I just copy paste them in with no comment, usually that fixes it. The code grows beyond my usual comprehension, I’d have to really read through it for a while. Sometimes the LLMs can’t fix a bug so I just work around it or ask for random changes until it goes away. It’s not too bad for throwaway weekend projects, but still quite amusing. I’m building a project or webapp, but it’s not really coding - I just see stuff, say stuff, run stuff, and copy paste stuff, and it mostly works.

Re:Bun has an open PR adding shared-memory threads to JavaSc... by koolba on Sunday June 21, 2026 @12:25AM (#48615667)
It’s the same as non-vibe coding in 2026, but you stop pretending you wrote everything by hand.
Re:Bun has an open PR adding shared-memory threads to JavaSc... by senorrib on Sunday June 21, 2026 @12:31AM (#48615697)
No it’s not.
Re:Bun has an open PR adding shared-memory threads to JavaSc... by prymitive on Sunday June 21, 2026 @05:35AM (#48617233)
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 JavaSc... by adamddev1 on Sunday June 21, 2026 @11:03AM (#48619552)
I shouldn't have used the term "vibe-coded" as that's an extreme charicature. But I would argue in general heavy use of LLMs just does lead to sloppier code, and I think there's a general feel for that. Has AI use helped Microsoft make better software lately?

People live to benefit from AI for their own work, but are understandably uneasy about depending on code written by AI, even if it's (mostly) human reviewed. 2-3% more bugs may not seem like a big deal, but when you start building stacks of things these bugs bubble up and increase exponentially.