4 ms·

That's just false. Just because it's open source doesn't mean Automattic doesn't want to turn into a SqaureSpace model. There is no doubt in my mind that the pi

That's just false. Just because it's open source doesn't mean Automattic doesn't want to turn into a SqaureSpace model. There is no doubt in my mind that the pivot and ramming through of Gutenberg is because they are scared of things like SquareSpace and feel they need to evolve fast. They do need to evolve, but they also need to stop cutting corners and listen to the community...It won't be long (it might already be true) that the "Classic Editor" plugin will have more active installs than any other plugin in the repo. That's a LOUD message from the community that "this is not ready!" I have sites that are Gutenberg compatible but I still have the classic editor on, because it's a giant mess. Gutenberg from my experience is a server hog compared to the classical Wordpress. It's harder on database servers and on memory. Yet they won't even change their PHP practices to make it 7+ requirement.

photomatt 8y ago
There's also facts: Gutenberg plugin adoption is growing faster than Classic Editor adoption, so it's not likely it will have more active installs than any other plugin. But even if it did, that's okay, we're supporting it. It's not a failing of Gutenberg, just showing that people for whatever reason don't want change. AFAIK there is no change to database or memory usage post-Gutenberg, especially since pretty much all of the new code executes on the client side when you edit a post. It may use more memory in your browser, but not anything that should cause issues.
bph 8y ago
The conclusion that sites installing the Classic Editor won't adopt to Gutenberg has a logical flaw. The Classic Editor is also used for sites, that are not "ready" for Gutenberg because it uses plugins that haven't gone through a full compatibility tests or where the site owner decided not to jump on the first version of WordPress 5.0 and waits until the kinks are out, say until 5.0.2 or 5.0.3. So there might be a lot more installs of the Classic Editor plugin coming, just because of this normal hesitance to jump on a new software feature out of the gate.

photomatt 8y ago

There's also facts: Gutenberg plugin adoption is growing faster than Classic Editor adoption, so it's not likely it will have more active installs than any other plugin. But even if it did, that's okay, we're supporting it. It's not a failing of Gutenberg, just showing that people for whatever reason don't want change. AFAIK there is no change to database or memory usage post-Gutenberg, especially since pretty much all of the new code executes on the client side when you edit a post. It may use more memory in your browser, but not anything that should cause issues.

bph 8y ago

The conclusion that sites installing the Classic Editor won't adopt to Gutenberg has a logical flaw. The Classic Editor is also used for sites, that are not "ready" for Gutenberg because it uses plugins that haven't gone through a full compatibility tests or where the site owner decided not to jump on the first version of WordPress 5.0 and waits until the kinks are out, say until 5.0.2 or 5.0.3. So there might be a lot more installs of the Classic Editor plugin coming, just because of this normal hesitance to jump on a new software feature out of the gate.