oh great... they're still touting raw, editable html as if it's "structured data".

so, when the html needs to be updated to meet evolving standards or different design choices in a redesign, it means modifying every post everywhere, and because these blocks can be modified as raw HTML, any automation created to do so is likely to get hung up on "modded" blocks.

Data Structure and HTML output should never be combined. The result is a mess that fails to understand that the finer points of output syntax will vary based on context.

Imagine trying to render an HTML email template from a Gutenberg post, and you'll understand the nightmare this storage method leads to. On Github, they're are arguments as to whether column blocks should be based in flex or in row/column markup. If you want to make a compatible email, the answer is still html tables. Maybe they should use that for columns in every context, to be compatible?

but, despite all logical criticism, the ship of feceus sails on into the maelstrom.