I don't think anyone is talking about it because it's not a very productive conversation to have. I'm not particularly bullish on vibe coding either but if you could explain what exactly about vibe coding causes these specific issues then it could be more interesting to discuss.

But as it stands, the more likely reason is capacity crunch caused by a chips shortage and demand heavily outpacing supply. You vibe coding reason is based on as much vibes as their code probably is.

If an AI doesnt generate perfect code, if left to its devices it will at some point create a codebase big and nasty enough that it will not be able to deal with it.

that is a separate issue indeed, but their comms make it rather obvious they are scrambling to reduce compute and they're just slashing their service selectively - with openclaw and max users being the first in the chopping block

It should catch up faster. It's absolutely useless for the bulk of the tedium—notably, soldering together random repos to satisfy executives—that makes up my job now.

That's not an elephant in the room.. it's just proof of how insanely useful the tool is and the reality that so much more hardware is needed. Thus people saying "why are these companies building insanely large data centers" ... this is why!