33
How Vibe Coding Is Killing Open Source
(hackaday.com)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 02 Feb 2026
33 points (97.1% liked)
Technology
81700 readers
731 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related news or articles.
- Be excellent to each other!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
- Check for duplicates before posting, duplicates may be removed
- Accounts 7 days and younger will have their posts automatically removed.
Approved Bots
founded 2 years ago
MODERATORS
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.
Might make open source more trustworthy, It can't be any harder to check than closed source.
A week or two back there was a post on Reddit where someone was advertising a project they'd put up on GitHub, and when I went to look at it I didn't find any documentation explaining how it actually worked - just how to install it and run it.
So I gave Gemini the URL of the repository and asked it to generate a "Deep Research" report on how it worked. Got a very extensive and detailed breakdown, including some positives and negatives that weren't mentioned in the existing readme.
Yeah, LLMs do a decent job explaining what code does.
I don't know yet how good Gemini about it,but I think https://deepwiki.com/ this tool will overkill anything for now
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.
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.
✨ especially this one ✨
Is the ✨sparkly emoji✨ the <BLINK> of the 21st century? Discuss.
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? )
_ /\ _
Check out this one I came across earlier - https://github.com/Jtensetti/fediverse-career-nexus/blob/main/README.md
It's a federated LinkedIn. ofc it's vibe coded.
Man... of all the vibe coding tools, Lovable has gotta be one of the most useless, too.
I work with people (all middle managers) who love Loveable because they can type a two sentence description of an app and it will immediately vomit something into existence. But the code it generates is an absolute disaster and the UIs it designs (which is supposed to be its main draw) is some of the most generic crap I've ever seen.
0/10, do not recommend.