I understand your point of view.

I'd like to offer our opinion. As a small web agency we are only just discovering the possibilities of Gutenberg, we clamped onto the Classic Editor for a while.

But since some months we add Gutenberg blocks to our themes, using the features of Advanced Custom Fields. Indeed, this will lock the client into the specific theme. But the sites we build for these cliensts are custom designed for them, and therefore meant for a single purpose. This also means the available custom fields, post-types and taxonomies are specifically added for that client.

For these clients, to be able to switch themes is not a goal. The custom blocks are also not meant to be used by other users, since they rely on the custom fields, custom post-types and custom taxonomies we added for the specific theme.

A big discrepancy onto the article, is that we don't publish our themes, plugins and blocks for general use. They are distributed through Git and GitHub Updater and only available to the specific client. Therefore I guess there can't be any misunderstandings for other people, because they won't stumple upon them anyway.

But, in the end, I share your opinion. I'd like the blocks to be theme and plugin independent, so after years of good use, we can build a new theme for the client and just use the same content (and blocks).

So thanks for publishing your opinion, we will look into it.