Only until AI investor money dries up and vibe coding gets very expensive quickly. Kinda how Uber isn’t way cheaper than taxi’s now.
Submitted 5 hours ago by mesamunefire@piefed.social to technology@lemmy.world
https://hackaday.com/2026/02/02/how-vibe-coding-is-killing-open-source/
Comments
WanderingThoughts@europe.pub 5 hours ago
Zwuzelmaus@feddit.org 31 minutes ago
until AI investor money dries up
Is that the latest term for “when hell freezes over”?
blaggle42@lemmy.today 4 hours ago
This.
percent@infosec.pub 2 hours ago
I wouldn’t be surprised if that’s only a temporary problem - if it becomes one at all. People are quickly discovering ways to use LLMs more effectively, and open source models are starting to become competitive with commercial models. If we can continue finding ways to get more out of smaller, open-source models, then maybe we’ll be able to run them on consumer or prosumer-grade hardware.
GPUs and TPUs have also been improving their energy efficiency. There seems to be a big commercial focus on that too, as energy availability is quickly becoming a bottleneck.
XLE@piefed.social 31 minutes ago
Can you cite some sources on the increased efficiency? Also, can you link to these lower priced, efficient (implied consumer grade) GPUs and TPUs?
WanderingThoughts@europe.pub 1 hour ago
So far, there is serious cognitive step needed that LLM just can’t do to get productive. They can output code but they don’t understand what’s going on. They don’t grasp architecture. Large projects don’t fit on their token window. Debugging something vague doesn’t work. Fact checking isn’t something they do well.
TropicalDingdong@lemmy.world 4 hours ago
Vibe coding is a black hole. I’ve had some colleagues try and pass stuff off.
What I’m learning about what matters is that the code itself is secondary to the understanding you develop by creating the code. You don’t create the code? You don’t develop the understanding. Without the understanding, there is nothing.
Feyd@programming.dev 4 hours ago
Yes. And using the LLM to generate then developing the requisite understanding and making it maintainable is slower than just writing it in the first place. And that effect compounds with repetition.
Paragone@lemmy.world 2 hours ago
TheRegister had an article, a year or 2 ago, about using AI in the opposite way: instead of creating the code, someone was using it to discover security-problems in it, & they said it was really useful for that, & most of its identified things, including some codebase which was sending private information off to some internet-server, which really are problems.
I wonder if using LLM’s as editors, instead of writers, would be better-use for the things?
_ /\ _
MadMadBunny@lemmy.ca 5 hours ago
How AI is killing everything.
statelesz@slrpnk.net 5 hours ago
LLMs definitely kills the trust in open source software, because now everything can be a vibe-coded mess and it’s sometimes hard to check.
RmDebArc_5@feddit.org 5 hours ago
LLMs definitely kills the trust in
open sourcesoftware, because now everything can be a vibe-coded mess and it’s sometimes hard to check.bryndos@fedia.io 4 hours ago
Might make open source more trustworthy, It can't be any harder to check than closed source.
rozodru@piefed.social 4 hours ago
yeah it’s to the point now where if I see emojis in the readme.md on the repo I just don’t even bother.
Paragone@lemmy.world 2 hours ago
ttbomk, emojis are legal function-names in both Swift & Julia…
The Swift example was damned incomprehensible, & … well, it was Apple stuff, so making it look idiotic might have been some kind of cultural-exclusivity intention…
The Julia stuff, though, means that you can use Greek symbols, etc, for functions, & get things looking more like what they should…
Also, I think emojis are actually better than my all-text style, for communicating intonation/emotion ( I’m old: learned last century ), & maybe us old geezers ought to adapt a bit, to such things…
That does NOT mean that cartoon “code” is good-enough, whether it’s cartoonish in plaintext or in emojis, though…
I’m just trying to keep the cultural-prejudice & the code-quality being distinct-categories of judgement, you know?
( & cultural-prejudice is an actual thing, though it’s usually called “religious wars”, isn’t it, in geekdom? )
_ /\ _
rimu@piefed.social 4 hours ago
Check out this one I came across earlier - https://github.com/Jtensetti/fediverse-career-nexus/blob/main/README.md
mintiefresh@piefed.ca 4 hours ago
I used to use emojis in my documentation very lightly because I thought they were a good way to provide visual cues. But now with all the people vibe coding their own readme docs with freaking emojis everywhere I have to stop using them.
Mildly annoying.
acosmichippo@lemmy.world 4 hours ago
or anywhere. Job descriptions for example.
Tetsuo@jlai.lu 4 hours ago
I think for someone that is very knowledgeable In a project they would probably somehow now if there is vibe coding. I think this will affect brand new projects but not that much of the older codebase. Even think it might enable finding old bugs in old open source codebase.
phil@lymme.dynv6.net 3 hours ago
Open source is not only about publishing code: it’s about quality, verifiable, reproducible code at work. If LLMs can’t do that, those “vibe coding” projects will hit a hard wall. Still, it’s quite clear they badly impact the FOSS ecosystem.
whereIsTamara@lemmy.org 3 hours ago
This isn’t the problem with the AI, it’s the problem with the user. If you don’t know enough to select the library and make the AI use it, maybe you were never gonna finish the project without AI anyway.
RalfWausE@feddit.org 19 minutes ago
If the abominable intelligence is killing every corner of things we consider good its time to start killing the “AI”…