My opinion

  • I have used www.ads-software.com for developing my own sites for people since 2008.

    After reading the comments on both sides of the issues of whether or not to use Gutenberg, my feelings are this:

    Like many developers here that have expressed their concern about whether or not to use the Gutenberg editor, I have decided to opt out and not use it for the simple reason that I don’t need to use it. My websites have already been built many years ago, so there is no reason for me to be forced into doing redesigns or bug fixes. I will be using the Classic Editor plugin for all my existing installations. This way, I don’t have to worry about anything because I will have that backward compatibility.

    I have been told that the Classic Plugin will remain available to anyone who needs it and can ensure in it’s continued maintenance. I would like to see proof of that. Will the WordPress development team announce that? I have read much concern about that and I can understand why. From what I’ve read in the WordPress developer’s comments, “There’s always the Classic Editor to help you get ready for Gutenberg.” It gives me the impression that the Classic Editor will be temporary, so I would like some clarification about this.

    If you are a person running a business with your WordPress site, (and thank God I’m not one of them), I would be concerned with whether or not the classic editor will remain available indefinitely.

    I have tried Gutenberg on a test site at my leisure and I have reported bugs over the prior months and then uninstalled it because I think it’s pointless to run it on existing websites where the design and information are static. When Gutenberg goes live in version 5.0, I’m assuming that there will still be bugs because it’s impossible to test every single theme with all combinations of plugins. So if someone’s site crashes as a result of Gutenberg, are you going to give 24/7 technical support to these developers and non-technical users? Are you going to reimburse them for lost revenue?

    My feeling while reading the WordPress developer responses is that that they have no intention of either stopping or postponing Gutenberg no matter what bug or problem is given to their attention.

    So, I think some of the ideas presented here by other people seem like reasonable concessions.

    1. Keep Gutenberg as a plugin.

    2. Allow Gutenberg to go live in WordPress version 5.0, but keep it in new installations only. Keep the current version of WordPress with the Classic Editor as permanent as it is now, and just give security upgrades, not feature upgrades in future releases.

    I don’t see why there can’t be a concession that will make all WordPress users happy. All this stress is unnecessary.
    Why can’t anything be done?

    Thank you.

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author Tammie Lister

    (@karmatosed)

    @lauritasita thanks for taking time to leave such considered feedback. You are correct that the Classic Editor plugin will stay around, that’s always been something stated by this project. As WordPress 5.0 happens, it’s not happening yet, this will also be said clearly along with the release.

    Thanks for reporting the bugs you have with Gutenberg. Whilst I understand you are choosing to not use it, the contribution you have made in reporting bugs is really great.

    Thread Starter lauritasita

    (@lauritasita)

    I have read that the Classic Editor Plugin will only be supported until December 31, 2021, but hopefully after that, it will continue to be supported beyond that if the need is great for developers who still need it and their businesses depend on it.

    Maybe @karmatosed could weigh in on this since it is very important to many users who want to continue to use it.

    Moderator Marius L. J.

    (@clorith)

    Hiya,

    I’d be happy to provide some information here!

    The Classic Editor plugin has been guaranteed to be supported until 2022, at which point it will be re-evaluated if core should keep maintaining it based on use, if better solutions exist etc. If it’s not within the scope of core to keep supporting it, there are many capable developers in our community that would be accepted as maintainers if they wished it, so I am confident it will keep functioning for some time even after the originally tentative date.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘My opinion’ is closed to new replies.