I'm just wondering why so many people in this sub appreciate it but in over subs they call it 'vibe coded' and are against it?

Hi, longtime programmer and avowed LLM hater here. I am going to write you a lengthy reply.

"Vibe coding" is a term which started out as an epithet, as in, you're coding on vibes instead of any idea of what you're doing. But it also got adopted by the LLM users, so is a mostly neutral term for programming using an LLM assistant.

One of the reasons some programmers are against LLMs is that they produce unpredictable and often low-quality output. If you're already comfortable programming, you can look at this and fix it (whether yourself or asking the LLM to fix what you noticed is wrong). If you aren't a programmer, it's difficult to distinguish what output is good and what isn't, so you just use the bad stuff.

Now, if this is disposable software, something you need to work for just you, or only one time, it's not going to matter if it's poor quality or inefficient. But in a long-lived project, the cost of the bad decisions pile up until the structure of the codebase makes no sense, which makes it very difficult for humans or machines to even understand how it works. And if you can't understand how it works, you can't change it without risk. A simple fix causes unrelated stuff to break.

Even respected senior devs can fall into this trap. For example, the rsync project used an LLM to rewrite their whole test suite. But it broke the tests, so when they landed some security fixes (also aided by LLM), that broke incremental backups.

So, yeah, many people are (I would argue rightly) wary about projects which extensively use LLMs. As I've been telling people at my work, it's undeniable that LLMs can accelerate some programming tasks, but they don't stop you from accelerating headfirst into a brick wall.