I think the majority of developers would agree the existing editor needs modernising. Clients would love a few tools to help them write and "just drop in a table", or "just make each Profile photo align with their bio"
Developers in the past have had to rely on TinyMCE buttons, MetaBox solutions and CPTs to solve the smallest problems. So, I think most developers were excited when we first heard of Gutenberg because we were looking forward to an elegant solution. We expected to have fewer onerous requests from clients who would be using a faster and more powerful editor.

So our problem is not that Gutenberg exists. It's that we are disappointed in the outcome. Automatic and the core team had the best intentions but some early decisions have sadly taken this "Ship" far off course. That sort of thing happens to all of us and we all recognise the signs, it's just unfortunate that it's happened here.

One (small) example:
The early choice that paragraphs and headings should always be discrete blocks has given us a situation where a medium sized article requires many blocks and many blocks mean many editors and that slows the author's typing to a crawl. Perhaps this will be resolved - but any author typing a long article in January 2019 is not going to be happy.

The other problem about the "paragraphs as blocks" choice is that the apparent aim is to allow the movement and formatting of paragraphs.
In normal writing the block-like movement of paragraphs is occasionally required, but cut and paste is the traditional solution and it covers more cases (move a word, move a phrase, move a sentence, remove a sentence, move a paragraph, move two sentences which span two paragraphs, etc).
There's little need for paragraphs as blocks until a transform or insert is required - but then why not have that action split the content. Don't start with 30 blocks, start with one and then split it or group it as required (I digress!)

Gutenberg currently assumes each H or P element is a discrete entity and potentially requiring a transform. Consequently, where the author might expect to be writing within a few movable & formattable blocks instead they have 37 editors lurking, each with subtly different controls - and the implementation of these editors is now so resource-heavy that Gutenberg itself struggles to deal with them.

I look forward to Gutenberg in 2020, by which time it will have hopefully have found its feet.