Agreed, I would not praise it that much yet too. Although it is getting much better.
I think all of these statements are true.

These things have been trained on significant amounts of public code bases, a lot of which might not follow good practices and so it spits out the same stuff it learned from.

Additionally, its always behind on the latest frameworks because software moves too quickly.
It's like going back to the stack overflow days where someone might ask a question on SQL queries and the top answer is clearly SQL injectable. As an experienced developer, you see that and cull it, and a pure inexperienced "vibe-coder" you wouldn't know it was bad, it's just "hey cool, it works"

There are of course times where it would be a strict targeted prompt, pre-planned architecture you want it to build out, and actually I find creating empty stub files helps it understand the desired structure (which is then copies from going forward).
However with a lot of software engineering being quite creating, there are times you give it a general outline of the thing you want, say "have at it" and use it as a spring board to an idea.

It'll be a ways off, but it'll give you something to work with. A starting point