Comment by sshine

> You stop trying to enforce this rule as it is a "fight" you can't win and dealing with this takes more effort than dealing with the issues the low quality vibe-coded projects caused in the first place

> You stop trying to enforce this rule as it is a "fight" you can't win and dealing with this takes more effort than dealing with the issues the low quality vibe-coded projects caused in the first place

Interesting observations.

The problem is not that they're vibe-coded.

The problem is that they're low-effort abandonware.

It's very hard to tell apart if something is going to get abandoned.

I certainly have more abandoned vibe-coded projects than non-abandoned ones.

But I also have ones that I use daily or weekly, and ones that have 30+ GitHub stars and open tickets and forks without I ever expected that to happen.

When I go looking for software that I need, life has become more difficult, because I need to ask myself if the project I encounter is going to get abandoned because of the low effort it took to manifest it.

Rather than judge how it's made as a proxy for how its future will turn out, judge its future: Require some kind of sustained lifetime and social engagement around a project before it is deserving of advertisement.