Dorsey

“Get yoast seo premium! Get yoast SEO premium!” Nagware is so bad i will NOT be getting the pro version and finally a competitor (rankmath) to use instead. Even imports my yoast SEO so nothing is lost in the transition. Not sorry yoast, I’m out.

Yeah, I paid for the premium version – my mistake!

I agree with Patrick also. Here’s 10 reasons why I won’t use it: First, I already have a page builder that came with my theme and it is 10x better than gooberg blocks. Second, I still see a difference in performance between 4.9.11 and 5.2.3 the non gooberg 4.9.11 being faster. Third, I’m still seeing incompatibilities with some plugins and themes. Fourth, I have a desire to stop using WordPress altogether, based on the responses from the WordPress team that I’m seeing online – essentially, “They don’t care if you don’t like it, you will use it!” They seem to be echoing the message they are getting from the very top. Simon Sineks’ “How great leaders inspire action” Ted Talk on youtube explains rather succinctly that people identify with “why” you are doing something before they consider buying or even using your product, The WordPress Foundation and Matt Mullenweg clearly have not seen this video! Fifth, The FOMO and the “you have to use the latest or risk getting hacked” diatribe is a fear based mantra, (I’m not going to cover F.U.D. here) and it’s totally false with the advent of the classicpress.com fork of version 4.9.x. Considering how bad WordPress was in the past with security, I don’t think they have room to even talk about that. Sixth, Not only do I despise the time lost on the block editor, I get to spend additional extra time explaining to all my clients what happened and why and how to fix their stuff that worked just fine until they updated WordPress. Seventh, a quick look at the Gutenberg block editor plugin shows almost 3,000 reviews and it has only a two star rating – those of us on this thread are a fraction of the unhappy users. Agile project management? anyone? eighth, the number of “disable blocks” and “downgrade WP” plugins and their use is on the rise. Plus the 5+ million ACTIVE users of the classic editor should tell you something… it has a 5 star rating BTW… Ninth, the 200 odd new “core” files created by the block editor show WordPress is growing like a kid eating cake. Tenth, do I really need 10 different reasons? No, I only need one or two. The fact that it’s inconvenient, buggy, incompatible and slow to actually use would be more than enough, but here’s the tenth reason; I see and hear the “you just don’t like change” argument thrown around. That’s a lie, that’s what Agile Project Management is all about! I love good change. I’ve watched some theme developers continually update their products with new features and knock it out of the park! They’ve added feature after feature that created a new learning curve yet they left their user base saying things like, “incredible! wonderful! Amazing!” I’m not hearing that about the block editor from ANYONE. So the tenth reason I do not like the block editor is because I haven’t been given one good reason why I should like it. Sell me this block editor… It’s easier to sell a pen in the digital age… I see no need, use, or value. I see no better features or added benefits. It doesn’t do anything to make my life better. It’s just not in the interest of the user community – if you don’t believe me just ask the other users. WordPress isn’t listening to it’s users though, this is a foreshadowing of things to come from The WordPress foundation. They did something so upsetting to their user base that they caused a fork of their own software, yet they make no apologies, get used to it or get classicpress.

• This reply was modified 5 years, 1 month ago by Dorsey. Reason: spelling and grammatical errors - I'm a developer not a blogger

I have to agree with you @arttuk. We have about 300 clients and the backlash has been overwhelming for our little team. Did WP users ask for a better editor? Blocks? We certainly didn’t. My clients don’t care why their site doesn’t work (plugin/theme incompatibility) or why it doesn’t work like it used to (gutengarbage), they just want to get work done (as do we) and this has been the largest hit to productivity since our company started in 2015. I see the same rhetoric from @designsimply about how this is a good thing… (unified across different areas – what does that even mean?) I’d love to send my support calls directly to you or www.ads-software.com. We use Divi as well, it’s the number one theme on the planet – you would think WordPress would work with their best allies to insure compatibility but even more than that, why why why did you say you were going to release it on x date and then not follow through with what you said, releasing it early? Most of our customers come from another vendor who didn’t keep their word or listen to their base, WordPress please don’t be like this. I welcome change. I like to grow. I also like backwards compatibility and better advanced notice. I especially like customer input and feedback. My suggestion moving forward is to adopt an Agile process management strategy – spend your efforts fixing the most requested things and drop the things people don’t like (hello dolly)