It really shows that Automattic has no idea who their customers really are or what they need.

WordPress is for:
1) Agencies developing custom websites
2) Non-developer power users who want a simple way to manage their site within the confines of their theme and plugins

WordPress is NOT for:
1) Full page editing and “designing” within the browser. There is wix for that and WordPress will never entice a single customer away from wix with its half-baked implementation.

If they implement Gutenberg properly to compete with wix and the rest, they would satisfy the third group but alienate the first two. Currently it’s a lose-lose-lose and it could potentially end up a lose-lose-win but the win is for a group that never was a WordPress user before.

Editing content within Gutenberg isn’t easier. It’s an absolutely pain in @ss. When you’re trying to edit a page that is largely text content, you typically don’t just want to move one or two paragraphs from here to there, by dragging ‘n dropping a block or two. You’ll quite often move sentences around from one paragraph to another, to make it easier to read. Limiting the Paragraph block to only a single paragraph is a real pain and makes it more difficult, and slower, to edit your content. It is significantly easier editing text heavy content, when all that text is within the same block, or even just a couple of blocks, which is what every other page builder allows you to do. Copying and pasting text from one block to another, is so much more difficult and a considerably slower way to edit content.

When you have a layout that contains a Group Block, which then contains other blocks within that Group, you can’t even reliably select the block you want. Gutenberg has been in Core for 2.5+ years now, and you still can’t reliably select blocks. It’s a block editor! This is the most fundamental thing that it should handle, but it doesn’t! Every single page builder out there, even the worst ones, let you easily and reliably select any block you want to edit, yet somehow Gutenberg still struggles with this basic fundamental usage. It really shows just how poor the UI truly is when you still can’t even reliably select blocks.

Core developers promised that Gutenberg would, AT THE BARE MINIMUM, allow you to do EVERYTHING that the Classic Editor allowed you to do. They can’t even fulfill this one basic promised as there’s still Classic Editor features that don’t work in the Block Editor.

Every major WordPress release sees significant UI changes within the editor, which makes it incredibly hard for end users. How are users expected to get used to working with the Block Editor when the UI is constantly changing every few months. Millions of WordPress users around the world are basically being treated like beta testers with a new version of software every month. From day one there’s been too little thought put into the UI in regards to what features are going to be included in the Block Editor and how they’re going to work.

Perhaps instead of trying to force in Full Site Editing (FSE), while it’s still in its early days, the core developers should spend more time cleaning up and fixing the 3K+ issues that are still outstanding on Github, some of which were raised even before it was in Core. How about making the editor a better experience for the millions and millions of people currently using WordPress, rather than forcing in new features every couple of months, along with new UI changes.

I’ve always been a big supporter of using Core features, because it does make your site cleaner and leaner, but ever since Gutenberg was forced into Core in 5.0, before it was even ready, I’ve been forced to find a better way to edit my content. Thankfully there’s now quite a number of less buggy and better built Page Builders out there to choose from. Maybe one day the Block Editor will be a pleasant experience to use, but that day is a loooong way of.