ES version is available. Content is displayed in original English for accuracy.
Advertisement
Advertisement
⚡ Community Insights
Discussion Sentiment
42% Positive
Analyzed from 2401 words in the discussion.
Trending Topics
#code#vibe#coding#projects#don#coded#more#real#project#software
Discussion (68 Comments)Read Original on HackerNews
Using coding agents to search for patterns, understanding why our abstractions might not be working because of how users integrate, etc etc.
Not everything vibe coded is bad software, not all bad software is vibe coded.
They are trying to avoid that.
Your process doesn’t sound like vibe coding to me, though maybe this part is “and even write code that I would never write”. If you’re just generating snippets as black boxes and putting that into a project you’re otherwise maintaining general understanding of, this isn’t what I refer to as vibe coding. (Not that I’d use this process in a community with clearly stated rules against AI use.)
FWIW, if an LLM is writing significant code, I'd consider it vibe coding regardless of your understanding of the code or expert guidance and almost certainly ban-AI people would too. The scale people seem care about when this comes up is code percentage that's LLM-written to hand-written, not code ignorance to full understanding by the author.
Then they should not be in the business of hosting repos?
A ridiculous take
Some would say I a, vibe coding since I don’t really write the code. I say I’m not because I’m thinking through the features more than vibe coders.
Coding is just going to be asking for a result and manually testing it, no real thought about what code has been generated, and no human should ever need to look at or review it. Even some versioned tarball on s3 will do for the storage.
So, really, who cares about what they do when their entire business model (and Github's) is speedrunning becoming obsolete?
Basically, the future of tools like github is a platform for manual testing, where the AI proposes a change and you can experiment with the UI and attach notes for the next iteration. The whole idea of coders carefully reviewing the output of LLMs is insane, it'd be like carefully poring over the output of GCC; we've made lines of code so cheap and skill-free that there's no point in these platforms that treat code like it's important to view.
From that perspective, it makes sense to limit "vibe-coded" projects, since they don't fit in that traditional paradigm.
Now, there are big feelings around vibe-coding and a strong aversion to change, so I can imagine this is a rather jarring experience for folks that want to vibe-code and want to have the dopamine hit of sharing that with other folks in a forum that obstensibly is meant for folks to edit code together.
2 - How do you enforce this?
You make 10 commits over the weekend once a month for your fun side project, they won't police it (my assumption they can't and won't).
Your slop machines are running day and night, pushing hundreds of commits a day, day and night... You will get on their radar, take a look, then determine "yeah, this person can go somewhere else".
That's literally all I see out of these types of moves by people/organizations. A will to power and a sort of childlike insecurity that they might be replaced. These folks aren't ok.
And people who feel entitled to free compute/storage are way worse.
If this happens, one could imagine that the former will seek to use the code from the later for "training AI"
The later might charge the former a license fee
I was a little surprised that some people were outraged that Codeberg (strong ideology/principles) banned generative AI output.
Now that Sourcehut (craft-oriented?) is considering doing similarly, will there be be similar pushback?
These kinds of ideological purity tests and the weird bureaucracies and little fiefdoms associated with them are anathema the hacker ethos.
But look at the comments and discourse around this. I guarantee you it ain’t about the money.
My anecdata tells me that most of these vibecoded projects are one offs or abandoned. That’s not to say they don’t have value to the people who put them together. What I’m wondering though is: “Do these have enough value to the community to justify the cost of more infrastructure?”
My guess is the answer is no. Then in which case, if you need a place for your pet projects, Forgejo or Gitea should work nicely for you.
Isn't that true of human authored code?
Coding is turning into burger flipping -- you ask the computer to do something, then you do a bunch of manual testing. There's a little bit of jargon needed to ask for the right thing, but it's closer to flipping burgers than it is to rocket science.
From first principles a community that relied on high friction knowledge attainment as the barrier to entry does not survive contact with LLMs. That extends far beyond "programming" as well.
This for me the main source of concern. I am having a blast vibe coding. I understand my job is at risk. But I am totally oblivious to the fact that they are accelerating climate change.
The other sites may not be able to afford the infrastructure to support vibe coded projects. Maybe that is one of the reasons Sourcehut has this proposal.
Personally I agree with what codeberg did.
If it’s because it’s a source code storage service, that’s just not an interesting function. Run your own on a cheap vps with backups to R2.
Where is the line?
Drew draws the line of any introduction of AI in any OSS project. (1.) (2.)
Vim, Linux, OpenBSD have AI in them now, even a small tinge of it, so that would be considered slop.
Is it now with some effort with AI assistance that is acceptable or unacceptable or is it still slop?
Or is it more extreme that an OSS project should absolutely not have ANY AI at all to comply with not being slop?
(1.) https://drewdevault.com/blog/AI-in-Linux/
(2.) https://drewdevault.com/blog/Forking-vim/
I don’t even use LLMs, but these puritanical stands are a real turn-off. I got into FOSS because I don’t want anyone telling me what to do, not so I can be the one who tells other people what to do.
There’s a big chunk of the FOSS community that has dedicated itself to the cultural left “omnicause,” which seems to require full agreement with the consensus as one of its membership criteria. The thing is, even though I agree with many (but not all) of its tenets on paper, I don’t really agree with the methods used or the insistence on full agreement.
I also just despise ordinary politicking, and prefer slow procedure-driven decision making (like Debian) or projects driven by a visionary leader (like OpenBSD). This makes me an outsider by default. Projects that attract these people tend to engage in vicious struggle sessions any time there’s a serious disagreement.
I think the biggest schism I have with these people is over identity. I prefer to have no identity. Anonymous (or pseudonymous), faceless. They want to enforce a strong identity, even if it’s a constructed identity. It can’t just be about trust, given how often identifiable people break each others’ trust. I suspect it’s about enforcing ingroup signaling as a criteria of membership, in order to make the group look stronger and drive out dissenters.
https://blog.codeberg.org/protecting-our-floss-commons-from-...
And a repo of tainted projects and untainted alternatives.
https://codeberg.org/ethical-foss/open-slopware
May everyone find their niche but inclusion does not work when barrier to entry is reduced to near zero.
This is a new one. "Main use" indeed!