In reply to Steven Gliebe.

I don't think Gutenberg will crash WordPress, but I do think it will alienate and disenfranchise many developers along with many business owners. I think it will crash many sites and steer alot of users away from WP, and I don't see how Gutenberg will be easier for hobbyists/small business owners to use than the Classic Editor was/is. I don't see how WP can compete with Wix, either, this late in the game with a completely counter intuitive and buggy version of a pagebuilder that (let's be honest) cannot build agency-level sites the way that current WP can (albeit with plugins and a pagebuilder like Divi or BeaverBuilder).

If Drupal wants to adopt some portion of Gutenberg, that's fine. If Gutenberg is great, that's fine. I'm focused more on preserving a current roster of client sites and then finding a way to work going forward that isn't filled with a unstable, unpredictable roll out of a janky sort-of-pagebuilder that you could never train clients with.

As far as why not using Classic Editor and let the updates just roll on out...we all know that that path can be fraught with a) bugs galore, b) potentially serious issues with formatting, c) plugin bugs, and so on, while Automattic Inc figures out how to try to get Gutenberg operational. Long run, fine, short term, lots of drama and headaches, when you want to be rolling out clients, not bug patches all the time.

I'm very grateful for the ClassicPress fork because at least it provides an "escape hatch" from the madness of update, fix bugs, update, fix bugs, wash, rinse, and repeat cycle, while one guy tries to figure out what direction WP should go in in order to try to catch up to Wix. Imagine issues with Classic Editor, Gutenberg, or your pagebuilder or any given plugin breaking your site or jacking your site formatting while fielding client calls or losing leads the clients want or a site going down for days while you try to figure out why something isn't working as it's supposed to.