In reply to Daniel Olson.

I'm with you in having thoroughly tested Gutenberg I see a lot of things I like. Unfortunately it lacks badly in what it leaves out and where it does not address some fundamental things that should have been dealt with in WordPress years ago, one not having a better code code text editor experience bulit in.

The other big one is how WP5 will implement the current editor (Classic). Having to use a convoluted plugin to deactivate the block editor is overkill and quite frankly a sledge hammer when a one line filter tied to an on/off switch in writing settings would do the same thing. Only activating the block editor for new installs and leaving older installs would have be better PR for the GB team. Not stating a concrete date for Classic removal would also help.

Immediately though, Gutenberg's biggest problem is usability. Trying to locate and manipulate content buried in blocks, especially once you get into column structure and nesting is not fun. If they can crack that usability issue it would be a big step forward. But, until that happens, thinking that that the block editor will be easy for the average user, compared to the current TinyMCE with metaboxes setup, is delusional.