Comment on The New WordPress Editor: What You Need to Know About WordPress Gutenberg by Frank McClung

In reply to David Artiss.

Thanks for replying David. I feel your response is typical of the responses I've seen from the WordPress Gutenberg/Automatic team, especially the "...expectation that they would make any required changes during the natural lifecycle of their code". That's what makes it so frustrating for us who feel WP has been hijacked by an agenda.

The "expectation" means us, the customers and clients, will pay to make our sites work with Gutenberg, especially when it becomes part of core and replaces the current (I refuse to call it "classic" or "legacy") WP editor. And the fact that "many of your customers are already in contact" with you doesn't help the other millions of sites that must now convert.

Fork WordPress and/or keep Gutenberg as a plugin only, then everyone will be happy. Shoving Gutenberg down everyone's throats and then telling us we'll like it and must pay for the fixes/redesigns/etc. during a "natural lifecycle" doesn't bode well for WordPress.