Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Proposal to prohibit vibe coded projects from being hosted on Sourcehut

lists.sr.ht

Post reply on HN
Print view View original

21–30 of 101 posts

Re: Proposal to prohibit vibe coded projects from being hosted on Sourcehut

#21

Post by a2ff6eeb0 »

websap wrote: post #7

Yikes! I've been a software engineer for over a decade, and I've never had more fun in my career. Running an AI assistant on a cloud machine to pair with me, explore my ideas, learn new tricks, and even write code that I would never write due to timelines and deadlines has been fantastic. Using coding agents to search for patterns, understanding why our abstractions might not be working because of how users integrate…

Why would you ever care about looking at code? Code forges aren't really a useful tool going forward. As agents replace people writing code, the features of code forges really aren't that useful. Nobody will be reviewing agent code other than agents, and you don't need a pull request and code review model for that.

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.

Re: Proposal to prohibit vibe coded projects from being hosted on Sourcehut

#22

Post by acedTrex »

chinathrow wrote: post #17
cautiouscat wrote: post #10

Earlier quoted context omitted.

I don’t think their concern is “vibecode = bad” but more like they can’t handle the volume.

> I don’t think their concern is “vibecode = bad” but more like they can’t handle the volume. Then they should not be in the business of hosting repos?

"if you cannot handle a 10x load over the historical standard of generally low quality content you should not be hosting repos"

A ridiculous take

Re: Proposal to prohibit vibe coded projects from being hosted on Sourcehut

#23

Post by GPerson »

websap wrote: post #7

Yikes! I've been a software engineer for over a decade, and I've never had more fun in my career. Running an AI assistant on a cloud machine to pair with me, explore my ideas, learn new tricks, and even write code that I would never write due to timelines and deadlines has been fantastic. Using coding agents to search for patterns, understanding why our abstractions might not be working because of how users integrate…

What does vibe coding mean to you? I use the term vibe code to mean software produced by conversation with an agent, with minimal or no understanding of the code / project structure by the person.

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.)

Re: Proposal to prohibit vibe coded projects from being hosted on Sourcehut

#25

Post by serial_dev »

jorisw wrote: post #13

1 - Where does vibe coding end and agent-assisted engineering start? Where's the line? 2 - How do you enforce this?

Probably they go by volume...

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".

Re: Proposal to prohibit vibe coded projects from being hosted on Sourcehut

#27

Post by a2ff6eeb0 »

sscaryterry wrote: post #2

We are seeing the slow death of social coding. This policy is not inclusive in any way, and paints everyone and everything with the same brush.

We're seeing the death of people writing code. There's no reason for a human to care about what the computer executes, as long as it does the right thing, so why would anyone care about reviewing the 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.

Re: Proposal to prohibit vibe coded projects from being hosted on Sourcehut

#28

Post by dpmartinez »

What is considered vibe coded and slop?

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/

Re: Proposal to prohibit vibe coded projects from being hosted on Sourcehut

#29

Post by a2ff6eeb0 »

boxed wrote: post #5

> LLMs are harmful to the free software ecosystem as a whole, as their main use-case in software is to appropriate free software regardless of license and regurgitate it new new projects without any respect for the copyright, provenance, or obligations of the source material. This is a new one. "Main use" indeed!

Well, yes -- obviously; it takes a huge amount of training data and generates new projects. I guess you could argue that it's not just for new projects -- it's used for old projects too?

Re: Proposal to prohibit vibe coded projects from being hosted on Sourcehut

#30

Post by atmanactive »

seabre wrote: post #20
websap wrote: post #7

Yikes! I've been a software engineer for over a decade, and I've never had more fun in my career. Running an AI assistant on a cloud machine to pair with me, explore my ideas, learn new tricks, and even write code that I would never write due to timelines and deadlines has been fantastic. Using coding agents to search for patterns, understanding why our abstractions might not be working because of how users integrate…

To echo another reply in the thread, but with an example: have you seen the stats for OpenClaw on GitHub just for this week ?: https://github.com/openclaw/openclaw/pulse They are trying to avoid that .

Why is that bad?
Post reply on HN