Edited to add: I’ve now spent a very large amount of time with Gutenberg and created the 1,000th issue (at the time of writing) on the github repo. Conservatively I think it’s going to take around a days work per customer to teach them how to use this new system.
Charged out at our daily rate, you’re talking a conservative cost of £40,000 which we won’t be able to bill to our customers as this is “our” change. Multiply this out across the ecosystem and the costs of Gutenberg to business are astronomical. Let’s be conservative and say there are 20,000 other businesses in our situation.
Gutenberg is costing businesses £800,000,000. This is DISGRACEFUL. This is PURELY support costs.
We have invested hundreds (more like thousands) of man hours into making WordPress work just the way we like it and have reached a point where we can design and build bespoke websites in a matter of hours with very powerful features. We’ve baked all of this in using the hooks, actions and extreme amounts of customisation that we’ve all come to love at the core of the of WordPress.
Having looked at Gutenberg, the issues posted on Github, the reviews on here and the seemingly laissez-faire approach by the Gutenberg team towards the push back by the community I can only hope that a WordPress fork appears at 4.9. We have to upgrade WordPress to keep up with security issues, but this force feeding of Gutenberg is like the Windows 10 saga all over again – forcing changes that nobody wants.
Gutenberg is bringing in so many breaking changes to WordPress I can only imagine the cost to businesses across the globe. I wouldn’t be surprised if it is in the tens of millions in lost revenue.
Please please please don’t merge this into core. Listen to your users – make it a plugin, turn it on by default if you must, but please make it optional.
- The topic ‘Time for a WordPress fork?’ is closed to new replies.