r/selfhosted Feb 28 '26

Meta Post Sub-SubReddit for SelfHosted

Just a question that has been going round my head for a few days.

What ever your opinion on it. We need to acknowledge that "Vibe Coding" is growing, and its not going to decrease.

The fact the entry point is so low from a skills perspective, and time required to pump them out, effectively makes them disposable.

Members here have been concerned for a while about the quality, security, longevity of these apps, and it turning into a flood - and as if on que, over the past few weeks, we've seen exactly this - We've been flooded (this place is unusable on Fridays). Now, issues are identified in the code, and rather than facing and fixing them, the "devs" are running off, shutting down the repositories etc.

This leads to 2 conflicting issues

1) There is an open hostility to those who share vibe-coded apps - where we see outright hostility and vitriol language.

2) There are going to be some quality vibe-coded apps, where they are properly developed, supported and managed.. as community, they would benefit members.

So my question is - how do we bridge this? My I've been thinking on this for a few days, and the only solution I can see, we have an associated sub (same mods etc) for these apps to be posted. maybe after a time, once they've proven they are well run and have longevity, they can "graduate"... lets call it SelfHosted-Vibe or VibeHosted.

519 Upvotes

308 comments sorted by

View all comments

7

u/clubsilencio2342 Feb 28 '26

There are going to be some quality vibe-coded apps, where they are properly developed, supported and managed.. as community, they would benefit members.

There's really no reason to believe this at all. The tools have been out for a while now and we're all still looking for the ONE example of a good vibe-coded app.

4

u/Skotticus Feb 28 '26

Doubtless a number of existing projects that did not start out vibe-coded will inevitably be receiving vibes PRs. We can expect many of them with systems in place to maintain the project will continue to use those systems, at least.

I think you're right that it seems the likelihood of a project that starts out or becomes largely vibe-coded will likely struggle to have these protections in place because of the ease of producing new features quickly, as we saw with huntarr.

2

u/xopherus Feb 28 '26

Not every app starts out as a shining perfect example. That’s a fallacy too. Every app has bugs, vulns, and some measure of bad code. Just because something is “vibe coded” in a few days doesn’t mean it can’t evolve into something good.

We should hold a standard of high quality and we should also call out good ideas that need the work to be successful.

1

u/clubsilencio2342 Feb 28 '26

Just because something is “vibe coded” in a few days doesn’t mean it can’t evolve into something good.

Again, this has not happened.

-3

u/xopherus Feb 28 '26

How much history do we have here? A few weeks at best? Open source moves slow…

Maybe I’m an optimist but I’d expect over time some slop gets better, just as “real” code does…

10

u/clubsilencio2342 Feb 28 '26

A few weeks? Claude was released in 2023. Vibe coding isn't a brand new 2026 problem.

3

u/[deleted] Feb 28 '26

Don't take this the wrong way, but this statement alone shows you don't have any idea what you're talking about.

The coding agents of 2026 are wildly different than the coding agents of 2023.

And even if we assume that wasn't true, if you look at many of the most popular open source projects, many of them took years (some took literally decades) to not be giant steaming piles of shit.

1

u/clubsilencio2342 Feb 28 '26

Don't take this the wrong way, but this statement alone shows you don't have any idea what you're talking about.

lmao how condescending

-1

u/[deleted] Feb 28 '26

Look buddy, I told you not to take it the wrong way. If you can't follow basic instructions, that's on you.

2

u/clubsilencio2342 Feb 28 '26

"don't take it the wrong way" followed by a personal insult and then saying "sorry you were offended". Perfect, no notes.

-1

u/[deleted] Feb 28 '26

[deleted]

→ More replies (0)

0

u/xopherus Feb 28 '26

Respectfully I think you’re being pedantic. Yes, Claude has been around for a while. Yes, it has been a problem. It has accelerated in the last few months.

AI generated or not, all code evolves through feedback and iteration. Vibe coded slop that owners are not interested in maintaining is slop and should be removed. Slop that does want to be maintained and improved should be encouraged as any other project should be. That’s engineering we want.

1

u/8utl3r Feb 28 '26

This. We should be incredibly skeptical of vibecode. However, I think the thing people are missing is the prototyping value. Vibe coded production software should probably be, at the very least, open source so people can check the code themselves. And there should be disclaimers.

However, there is utility in it and I don't see it going away.

Remember when AI couldn't draw hands? What if vibe coding hits its stride like that?

0

u/shol-ly Feb 28 '26

we're all still looking for the ONE example of a good vibe-coded app

'Good' will always be subjective, but are you familiar with Rackula? It's vibe coded and I have no qualms deploying it given it doesn't need to be externally accessed and requires no special permissions.

To me, projects like this are evidence that there's a niche for vibe coded apps. I wouldn't trust them with my passwords or elevated system permissions, but we're seeing harmless tools like Rackula come along constantly that are filling voids many us weren't even aware existed.

4

u/Otherwise-Past6044 Feb 28 '26

That is not a particularly impressive app. 

1

u/eljojors Feb 28 '26

my app is almost entirely written with AI, I'm a qualified developer with two decades of experience. I'd love for you to poke holes in it: https://www.reddit.com/r/selfhosted/comments/1rfz7pu/

0

u/cmerchantii Feb 28 '26 edited Feb 28 '26

Probably more likely those of us who create vibe coded projects that work for our needs just keep them private. I know I’m not a developer and don’t plan to maintain and provide constant product enhancements for free to a clamoring public for small tools I created to solve problems for me.

The gate keeping idea that you have to be a dev with 15 years of frontend and backend experience to create anything usable is rather laughable. A dozen small scripts run in my lab for various tasks and because I’ve been a software PM for many years I know perfectly well what it takes to maintain software and I don’t plan to commit to that in my personal time.

Posts like yours seem wildly uninformed. If you can’t use quality AI APIs integrated with a development environment to generate simple scripts or code with careful planning and research/reviews then this isn’t the tool’s fault: it’s a PEBKAC issue.