Most slopcode projects are abandoned and deleted within months of release
(www.osnews.com)
from rimu@piefed.social to selfhosted@lemmy.world on 08 Jul 02:16
https://piefed.social/c/selfhosted@lemmy.world/p/2194586/most-slopcode-projects-are-abandoned-and-deleted-within-months-of-release
from rimu@piefed.social to selfhosted@lemmy.world on 08 Jul 02:16
https://piefed.social/c/selfhosted@lemmy.world/p/2194586/most-slopcode-projects-are-abandoned-and-deleted-within-months-of-release
This is why you should not install any of the vibe coded apps that get advertised in here regularly. You’re just creating a liability for yourself.
#selfhosted #slop
threaded - newest
I made the mistake of installing Starling recently, not realizing how it was made. I contributed a PR to it, wrote a few issues describing some showstopping bugs, and since then there’s been absolutely no activity from the creator.
That’s fine, they are under no obligation to work for free. But I wouldn’t have installed it if I knew it was abandonware.
Seems like your PR was merged by the creator? If you are mad that the creator isn’t doing anything with THEIR OWN project, fork it and fix it yourself… No need to get pissy and make a full complaint post in here about it.
It doesn’t sound like OP is mad at the creator, but annoyed at the increased number of projects that are abandoned
It’s hard to judge the longevity of a project, and LLMs can make a project look more stable and professional than it is. It’s fair to feel annoyed if you mess up that call and move your workflow to something that gets abandoned.
No one got “mad” or “pissy” or filed a complaint. I feel they they were very explicit that it was not a complaint.
Disagreed. You should blast and air everyone’s embarassing trash as loud as possible so no one misses it.
Are there any obvious signs of it being vibe coded that I’m missing?
In my experience, projects not being very active, especially small ones by a single person, isn’t anything new that has much to do with LLMs, it was always that way for hobby projects. And it was inactive for only about a month now, with the author replying within one day before that. I have a few hobby projects myself and don’t reserve time every month to work on them or check on their repos.
No obvious signs, nope. It wasn’t until I started using it in earnest that I got suspicious and then when trying to work on the code it became very clear.
The only slop worth using is slop you make for yourself.
That is so accurate. I have a couple of LLM-coded applications running, either because a solution wasn’t available, or existing solutions were beyond the scope of what I need, and would idle at up to 1 GB of RAM instead of 10 MB. In situations like these, being able to get a quick solution thrown together is such a boon.
@rimu this just seems like human nature in a nutshell. Easy come, easy go. If something had almost no impact on your life, didn't require you to commit and learn, then what value does it have to you?
Once you get past the gambling like hit of dopamine that is "wow it worked!?" from the code generator, there is no impact to you, no skin in the game. You at most want another hit, which each new part of the project will just give less and less as the scope gets smaller and the builds harder to reach.
Yes, I think that’s it.
Before LLMs, the effort required to get something into a releasable state was a filter that stopped people who aren’t serious.
Amazing that we trained kids to be addicted to slot machines in video games, which companies like facebooks zynga and other companies invested a lot of money in dark patterns and manipulating people into making purchased in games. The whole industry was going into that for a while. Raid shadow ledgends was made by some dude in Israel and has connections to a slot machine manufacturer, who is also on the American gaming commission which helped nudge regulators in the right direction.
That was years ago and now we have apps that are “ai prediction markets” that let you take bets on California wild fires.
Insanity is a world where the most vulnerable people are incentivised to commit arson so they can become a millionaire for 4 months before they blow it all on a home that’s too big for them, with a car and a truck thats too much for them, and no plan to keep up this life style other than more sports betting apps, or paying for “secret” insider knowledge for kalshi. Or these idiots think that because they’re listening to the right podcasts by some CEO loser that they’re going to make the right calls, not knowing they’re the ones getting scammed.
People are so ready to have all their jobs be just a slot machine that sometimes let’s you get a output you can get paid for. Then you send your vibe coded product to your client on some kind of gig job app and they’ll take their 30% cut. So after you had bad luck on your claude slot machine who kept making you reupt your token spins, and slopjobber app (all the recent fired Xbox and meta employees will work for apps like these) took its 30% cut you are left with 6 dollars for a hour and half of work. If its anything like uber eats they will use dark patterns where the harder you work the less money you make, and all the high paying jobs go exclusively to new drivers to hook them in. Yay ai progress. Oh yeah and because its ai this is all legal now, and the states aren’t allowed to regulate Ai so fuck you bud.
A solid 40% of projects get abandoned, that its about double for purely vibecoded is unsurprising. Purely generated is completely unmaintainable. At least they realized it within 6 months I suppose.
Hardly an issue with generated code. You could say the same about projects before LLMs were widely used for code generation: “most projects are abandoned within months of release”. The difference now is the scale and how some people feel about it.
Most hand-coded projects are “abandoned” within months of release, but this often happens because the project is done, not because the project outgrew the capabilities of the LLM and the vibecoder is too incompetent to fix the accrued technical debt themselves.
Nah, most projects where just abandoned. Most projects never reached maturity and where abandoed in like weeks if not days. Look at the amount of 0 to 10 star github repos that are open source and had no commits since ever. LLM’s just removed the hurdle to start something “simple” so now the problem just grew in size.
Plenty, possibly most, of those do exactly what they were built to do and nothing more or less. I have a couple of dozen such repos myself.
Hmm, I think we are running both on assumptions. This would need some data to be analyzed to actually have a clear picture.
There is a crucial difference though, vibe coding enables people who are neither interested nor capable of understanding what is involved in maintaining a piece of software. Before vibe coding it didn’t even come to this situation: if you can’t write software you don’t need to maintain it. While there were bad coders and bad maintainers before, the numbers have now increased dramatically because everyone can pretend to be a software dev these days.
I would say that the free tiers of those coding tools got cut back so much, that some of those slop coded stuff wouldn’t keep doing it any more.
Claude is on a 5 hr timer, and you get very few responses. Qeen Code was free for a second, that was nice.
Speaking from my own slop coded project viewpoint.
I expect this gap will be filled by cheaper models like GLM as they catch up to frontier models in their capabilities.
I believe they will catch up in no time.
But not every one will be able to pay anything for them.
I’m not paying because it is a hobby project (a huge one) and it is totally free with optional donations. That’s not much ROI.
Easy come, easy go
Even if they weren’t abandoned, you shouldn’t use them.
Well, yeah. There are lots of reasons. But basic self-interest is something we can all agree on.
Easy come, easy go
Vibe coding a simple project is easy, but a crapshoot, at the current state of LLM development. Vibe maintaining anything at all is basically impossibly currently, you need a competent developer for that.
Disagree. It’s perfectly viable. I’ve maintained several projects for over a year myself
Are these projects… in the room with us right now?
I’m not the one throwing out baseless accusations
Just baseless claims.
I have nothing to prove
Sounds interesting.
Can you link those projects please?
Oh here we go
I agree that people cannot vibe code well unless they are a developer. Knowing the difference between slop and using a tool to automate bulk writing code is crucial at the current state. And I don’t ever know if it’ll get better because you need to know why you want to build something someway.
The major issue I’m seeing with junior (and even intermediate) developers is that they trust that the AI will always do things the correct way and don’t question its approach, and they don’t develop proper debugging skills and just rely on the AI to attempt it.
To get decent quality output out of an AI model, you need to have critical thinking skills, at least basic knowledge of the overall architecture for whatever you’re trying to build, and enough knowledge to question the model when it does something wrong.
Blindly trusting AI is why so many old security issues are coming back - stored/reflected XSS, SQL injection, exposing databases directly to the internet with no password, things like that. Newer frameworks mostly got rid of them, and now AI is bringing them back. It’s a fun time for red teams at least.
On the flip side, if you’re vibe coding an app you should seriously consider whether it’s something you want to open source or make available publicly. There’s a social contract that comes with that.
I have 2 self hosted slop apps I build and maintain myself. I think people would genuinely get great use out of them.
…but then I’m inviting critiques and feature requests and am roped into supporting them so it’s not just a big pile of shit that wastes everyone’s time. And I don’t want to spend my limited free time making common sense improvements to improve it for others. I want to write a lazy Claude prompt with insufficient context, get it barely doing what I need, and then spend the rest of my time eating crayons and similar pastimes.
This is the attitude of an existing programmer who is using these tools. What I’ve found on here is a specific pattern that keeps repeating:
a social contract that comes with thatand think there’s something strange or accusatory/interrogatory when people ask questions they think are too difficult or technicalThere’s a clear disconnect. You’re talking about the homelab community which is a bit different but I specifically remember someone making an accessible Android UI and being extremely frustrated at people asking for the entire code to be released, and at people saying there’s not enough features there for that poster to be looping in advertisements on a fucking home page UI.
I get the impression that primarily-slop coders on some level think they’re doing programming, because of how you can get functional prototypes of code that is way above what a total beginner can write on their own. They think having code that compiles (whatever it’s usually Python there’s no compiling) means the hard part is over. They don’t seem to understand that the questions and concerns about vibe coding aren’t moral complaints but genuine concerns about liability, running code even the author doesn’t understand, and a complete cluelessness about what they should be doing to evaluate the code besides prompting it to be “good with no mistakes”.
That Android UI project seemed like a little thing a few people could install on their grandparents’ phones. It’s normal for the author not to understand every little thing. But being totally clueless and being offended at the suggestion, being entitled to put ads in it to get 0.0016 USD per year per grandma in exchange for taking up a quarter of her screen forever, not understanding why this looks scummy, why refusing to release 60% of the code looks scummy, why half the questions are being asked at all.
Again this would not be a problem if this wasn’t now expected for a significant portion of any projects you find online. A lot of projects are the first genuine effort of someone out there and they’re not perfect but they didn’t feel like the unceremonious implosion of the entire philosophical concept of personal computing.
And I’m fucking shit at writing good code and I’m pissed.
If someone isn’t motivated enough to actually think and create something, what makes you think they’ll be motivated enough to maintain that thing they didn’t create?
I’m generally anti-ai but this is kind of exactly what vibe coding is for.
Someone has a problem right now and there is no tool to fix their problem how they want it fixed, so they throw some shit together for personal use and maybe someone else can use it if they want idgaf.
Why would they maintain that? It does what they need it to, when they need it. Usually these tools are very basic.
I don’t disagree necessarily, but they shouldn’t be uploading / sharing one-off projects they don’t intent to maintain.
That is a bit of an open source philosophy difference.
Is it better that everyone has open source everything so that anyone who finds the one-off useful can benefit from it?
Or is the software actually not provided “as-is” like the license states and on releasing open source software the community deserves regular updates?
I think that second option is a very entitled path. We are not entitled to the continued used free labor of a random person on the internet.
Yes, but there’s a difference between having your source and binaries available on github and submitting to an app store like flathub.
If you read this community in the last weeks you’d know that slopcoders don’t stop at basic projects.
The pre-LLM-effort-was-a-filter argument holds up, but I think what effort was really filtering for was why someone built the thing. High effort filtered out “this seemed fun for a weekend” projects. LLMs just surfaced that those were always the majority.
The better filter is: does this project serve a specific audience that genuinely needs it, or is it a demo of what you can do with Claude?
What I look for now:
We build CircuitForge, self-hosted tools for navigating opaque systems (job markets, government benefits, insurance). The architecture is deterministic-first: eligibility checks, validation, and data pipelines are rule-based and grounded in structured data, so the LLM is drafting from a clean, repeatable foundation rather than hallucinating into a void. That also means we can run smaller, specifically fine-tuned models instead of throwing a frontier model at everything and hoping for the best. Smaller models run on consumer hardware, which cuts hosting cost and shrinks the privacy risk surface significantly. Humans approve before anything acts. Pipeline layer is MIT and lives on Forgejo. There’s a full devops stack, a real business model, and I use these tools every day. We’re also actively collaborating with other devs and always looking for contributors.
The people using these tools actually need them. That’s the commitment signal that doesn’t evaporate when the novelty wears off.
As always the social infrastructure (community, user base) is much more important for the success and use value of a piece of software than the exact technology used to make it (lang, framework, helper tools).
Just don’t install anything new after 2022. Easy way to get actual code audited by human beings.
It’s late and so maybe I missed it, but I didn’t see the part of the article that compares the abandon rate of slopcode with the overall abandon rate. Not saying that the premise is wrong or anything, but you can’t tell how bad something is unless you can compare it with the norm.
Also it’s again the false sense of security pf “if you don’t use vibed apps you’ll be fine”, making people forget basic security procedures.
I, for instance, had a service vulnerable and discontinued without noticing for months. It was something 100% made before LLM was a thing. Still had unpatched vulnerabilities and the project was abandoned. It was my fault for not checking more often is the services I host are safe or not.
I would guess that the key difference is that vibe coded apps can get to a more or less working state a lot quicker, while other apps are likely to be abandoned before it’s done.
Though in either case I’d always be careful with new projects. If it’s just a single guy that’s been working on something for less than a year and only have a handful of GitHub stars, I probably wouldn’t install it.
This is the main reason why vibe coding, even if it produces good code, is still a major problem. It encourages people with the goal of making software, but without the actual will and motivation to keep supporting that software to pump out software and publish it.
It’s like all the faceless AI-automated YouTube channels we have now. It’s not that these people had no way of doing it before, it’s just that it’s easy and might make them some money, or make them feel like they accomplished something until they get bored and move on.
There’s something to be said for convenient and easy to use things, but they’re a double edged sword, because they also directly target people with the least emotional investment to use them, as a side effect of that convenience.
TBH, most software will never be used my many so needs no support. Also, I think lack of long-term support is not the same kind of problem. It used to be any more. Back in the day when the original author dropped support it was a major investment to get someone else up to speed. Now fixes and enhancements can be done by LLMs as well, given a somehwat competent software developer.
But in general: The newer the project and the more bells and whistles it has, the less I personally would want to make it an essential piece of my workflow.
We went from “everyone will know how to code in the future” to “no one know will know how to code” pretty quickly
Vaporware is never not a thing.
I make all my own slop apps now. Bespoke crappy solutions for bespoke crappy problems. Abandmont rates are up, I can attest
Yeah same. I make loads of little things to bodge my own problems but would never be moronic enough to try and capitalise on something that took 60mins to make.
So what? The important datapoint is the number of new successful projects, not the number of the abandoned ones.
This isn’t the burn you think it is. Should we start listing actual high use hand coded abandoned foss projects?