This is not “just talk”. I’m opening this topic because while doing real things, I realized the following:
If we don’t introduce breaking changes, the WordPress ecosystem will do so anyway.
WP has an amazing back-compat history. But they are clearly resetting their back-compat base to WP 5+ now, which is going to leave CP behind, and which is nothing else but an extra motivation to start doing things differently.
At a certain point we will have to fork pre-gutenberg plugins anyway, because they will stop being compatible with WP 4.9 (and hence with CP).
Just an example: Contact Form 7, a very common plugin.
- Do nothing and wait for CP to die.
- Fork pre-gutenberg plugins (and allow the project to have some breaking changes).
Option 1 is inevitable. There is nothing you can do to avoid it other than update CP to be a copy of WP 5+.
Assuming option 2 is the way to go, this will allow to adopt some breaking changes, since most of the required adjustments will be minor adjustments, and it will enrich the native CP plugin ecosystem.
“Who is going to maintain them?” you will ask.
And I say… most well known plugins evolved together with WP from lower versions and achieved a mature state. They don’t need maintenance for them to work the way they already did. Anyway, if the native ecosystem gets richer, new devs will jump in and take control of their favorite plugins, maybe improve them with new CP features.