In reply to Matt.

That's a good response - thanks.

However, that response also feel like it needs to be prefaced with "When Gutenberg is all done and if it fulfills our desires... "

I'm concerned about the transition period. That period when Gutenberg isn't all that but is in core and how it will work for current themes and plugins. What will happen when a client just hits the Upgrade button (so to speak) on 5.0 and gets an all new editing experience? What happens for sites that use ACF extensively? Pods? etc...

I'm concerned that I see it being slated for 5.0 NOT for "when we feel it's ready".

I'm concerned that it's NOT just an editor revamp but introduces things like Columns which are layout.

I'm concerned that I can't seem to find a brief that describes who it's for and what problems it solves except, frankly, for this comment. When I search for it, what comes up isn't a product roadmap but a schedule one (https://make.wordpress.org/core/2017/08/11/revised-suggested-roadmap-for-gutenberg-and-customization/). For example.... which blocks are in for the first release? Are there more to come? Which might be dropped?

I'm NOT concerned that it's change. That broadside by some in this thread is passive aggressive nonsense. With 25 years in software, I've seen enough change to laugh at the idea that I'm afraid of it. I'm not. I'm simply aware of what it takes to ship quality software and slating it for 5.0 feels ambitious.

I'm also off to play with it more. Thanks for taking the time to reply.