So, it took the team almost a year to add a new page to the admin section and to update emojis. Emojis don’t belong to WordPress, they should be removed, along with the insecure XML-RPC protocol and the REST API. Also, custom logo design, which can already be achieved via countless plugins and simple hooks.
I don’t even want to mention the other changes, such as a PHP notice, a stray CSS .map reference. Really? Really?!
I was so looking forward to ClassicPress to actually improve the platform and remove legacy and useless code. I’m sure than in less than a month, an experienced developer could easily remove emojis, all obsolete code references, Flash, XML-RPC and REST. And there’s plenty more.
Here’s my list of WordPress features that should be gutted:
getbutterfly [dot] com/thoughts-on-wordpress/
Emojis, smilies, WordPress Capital P, oEmbed, pingbacks and trackbacks, Gravatars, declutter head, declutter widgets, remove support (and code) for PHP lower than 5.6 (with 7 coming next), remove SWFUpload, move XML-RPC and REST API to plugins (non-trivial, I agree), remove WordPress Password protected posts, tagline, post formats, post via email, update services, privacy policy, user contact methods (AIM, YIM, Jabber), keyboard shortcuts, jQuery dependency, jQuery Migrate, version parameter from scripts and stylesheets.
My hopes were so high with ClassicPress. I even migrated 4 or 5 sites to CP, but when I saw there’s no progress, I switched back to WordPress. I even started my own fork and almost removed everything I wrote above, but I don’t have the resources (time and motivation) to maintain and support a different fork.
Yeah, I have more to say, but I’ll stop here. I check the CP forums weekly to see progress, but I don’t. Hopefully, now that the holiday season is over, we’ll see more progress and more updates. But I won’t switch again until I see at least several updates with real progress. I don’t need to change my login logo, and if I do, I use a 10-line function in my plugin or theme.