To be honest, while I do think that romantic ideals were a relevant factor, I think page builders were a more pressing concern, and a desire to give editors more graphic feedback - in the "core concepts" there is a statement to think of blocks as "glorified shortcodes".

My main problem with the Gutenberg development process is that, in the beginning, it seemed largely decoupled from the needs of any user. When released, it was hardly usable for anything. As opposed to most page builders, it didn't even offer a simple UI to position elements relatively. All there was was the option to add a css class. And on the development side, the first useable toolchain came from outside the project itself. So much for "developer experience", even ignoring that developers were probably more attuned to php than to js/react at the time. That wasn't well executed, or communicated.

And even now, 3-4 years on, and with a clear commitment of the eco system to go down that road, there's still no clear way to simply do some things in Gutenberg that are a piece of cake in php. You yourself mentioned some earlier this year -https://github.com/WordPress/gutenberg/issues/32939

Talk about blocks as glorified shortcodes. Gutenberg is emphasizing page-contained visual content/editing over data input in editing masks/post types, for which it's not that important if the admin view equals the front end (irrespective of whether a static or dynamic templating system is used). I would say that the former is more relevant for personal sites while the latter is the bread and butter of most professional applications of the CMS.

Yet this very important part of the eco system hast not been given too much concern with respect to Gutenberg. There's a lot of talk about "better development experience" but the opposite is usually the case, not least because of a lack of usable documentation about how to code common things "the Gutenberg way", even if it's possible.

My hunch is that these things will be added, slowly, and I very much understand the strategic impetus for Gutenberg in all phases. But it would really be great if the communication could be changed to a tune that would make the people developing those currently "common" CMS things feel less estranged by Gutenberg. In my opinion, a lot would be already won by helping them develop things they develop today using the Gutenberg way.

I'm pretty sure, it would also help figure out some remaining problems with Gutenberg.