I'd say more of a commercial issue, creating your own walled garden is lucrative.

In defense of the "bad developers", many "good standards" seem to be deliberately inaccessible to anyone not joining the faith and making it their life's work to understand it. Standards that require a new vocabulary of already overloaded words and concepts are not that good. Often you can't know part of a standard and be better off for it. If you want wide adoption, don't target the narrow.

A good standard lets the bad users grow into better users. It's like the gap between novice vs pro graphics software. It's a novice trap. The novice software is so limited and "easy" that when a user needs a "pro" feature they have to jump off a cliff to learn a new universe--all at once. The "easy" novice software is good at keeping you there at that level. It often does nothing to prepare you for graduating to the next level. The gap is so wide that it hardly matters if you started off using the "beginner" software. Inaccessible pro software combined with beginner software that avoids teaching... it's just never going to be a pipeline.

Good developers are a rare resource yet we push back on efforts to improve mining them with gatekeeping. Part of the reason you are the "good" developer you are today is because there are so many tools that let you do bad things which became lessons.

If you want your blessed standards to change bad developers then you have to build in footholds for them. I think if you look at the poorly adopted "good" standards you'll find that there's a strong correlation with poor accessibility. Are you going to turn all the bad developers into good ones? No, but you might be able to elevate a chunk them to less annoying mediocre developers and I think that's worth it.

Is it really surprising that bad developers ignore good standards which ignored them? Good standards nudge rather than trap.

This subject is way off topic but let me try and bring it back in (a wee little bit). Yeah, I'm gonna coddle the common folk some more... We hate the vibe coding from the riffraff but we went out of our way to not vibe with them! I look at the vibe coding as desperate feature requests. If we want them to come to us "good" coders instead of the AI... maybe we need to meet them where the AI did. Maybe just a little? Is it taking our job away if we weren't doing that job to begin with?

The toasters be uncovering stuff and it's time to get creative... because we're the ones that are good at creative, right? TYFCTMTT.