Interesting article but where Gutenberg missed the mark is establishing a user interface guideline for Blocks from the start. Well, maybe they did and everyone ignore it...not sure.

What I find frustrating with Blocks is the inconsistency between collections where the settings/options available on one Block are completely lacking or arranged differently in another.

For me, and maybe others, this consistency is more important than "Bring something new to the existing Gallery block." After all, if I learn to use one block, I should have learned to use them all. I shouldn't have to hunt around for the placement of settings or wonder if the settings available in one Block is available in another.

Also, I suspect most people aren't going to use several Block collections on their site. They're going to choose the one that meets as many as their needs as possible and stick with it.

I've already run into problem where two Block collections conflicted with each other. I'm not going to name them or point fingers but I'm sure this will become more and more of an issue.

This is why I believe what Gerasimos said in his comment is so true. If you're a prominent theme developer, you'll need your own Block collection moving forward. If you don't have the resources to do so, then get in tight with an existing Blocks dev.

After all, if you're building sites with GeneratePress today, you're most likely going to use GenerateBlocks. If you're using the Kadence Theme, you're going to match it with Kadence Blocks.

I don't believe there will be a race to the bottom either. If anything, there will be a lot of abandoned Blocks and collections as people move into their respective theme ecosystem silos.