[photomatt]

We had it as an extension for a year and a half, and in that time it became the fastest growing plugin in WP's history. User tests also showed significant issues with our current editor approach and much better results with Gutenberg enabled, that's why some hosts have had it on by default since the summer.

I agree it's not for everyone, that's why there's an opt-out, but it is an improved experience for the vast majority of current and potential future users. It's shipped, and now we can continue to iterate on it.

[sparkzilla]

It might be fine for casual users, but it's really not good enough for those using WP to make sites for clients. That said, I wish you the best of success with it, and will continue to evaluate it as you progress.

[dpkonofa]

If Gutenberg isn't an improvement for you with regard to client sites, then you're not actually developing your client sites correctly per the WordPress specs. You're relying on builders to do too much of the work for you.

[sparkzilla]

Be serious. If I use a page builder, such as Enfold or Visual Composer, I can get a client site completed in much less time, with a consistent design, and with more precision than with Gutenberg. You're saying that I should use Gutenberg because simply because it is the WordPress Spec. But, as it stands, Gutenberg is simply inferior to page builders. IMHO that goes against the ethos of WordPress, which was always for extensibility i.e I can take my choice of competing plugins, themes and page builders according to the needs of my client and the project. Now, it looks increasingly like we're stuck with a system that is slower to use, delivers imprecise results, requires the download of overlapping blocks, is barely out of beta, AND that will destroy competition in the space. Even if it conforms to the "WordPress specs" that's not a good result.

[stevenicr]

If Gutenberg isn't an improvement for you with regard to client sites - NO, it is not an improvement for 50 out of 50 of our client sites. Not one person cares not 1 iota about it. It may actually break some of the custom themes some of them run, so it's the opposite.

"correctly per the WordPress specs" - this is like windows rolling out an update that breaks atom, sublime text, and others that were working well. Seriously.

We don't rely on page builders on 100 out of 120 sites. Some sites do have custom themes that incorporated rows for design, which may break with this update.

The sites that did rely on page builders were working great and had no need for Guten.

[stevenicr]

I wish people in the tech bubble would realize that "why there's an opt-out" - is like saying 'you can stop the beating by.." - why not just make it 'opt in" - when there is consent, side effects can be considered easier, and then there is more of a chance someone actually knows how to opt out / change the consent of this thing running.

[liveoneggs]

advertising it to everyone probably helped :)