Should you update to WordPress 5? This is a question that has been asked thousands of times in the past week. I have been asked at least a dozen times and every time my answer is the same. NO.
Unless WordPress automatically updates your site and it is more difficult to restore the prior 4.X release , then WAIT.
While the WordPress 5.0 editor, the most obvious updated to WordPress in the 5 release, is definitely a step in the right direction it is not a compelling reason to upgrade. Not too mention it is different. That means the content writing process you’ve gotten used to, including all the quirks inherent in WordPress, is going to have to be re-learned.
Vue is running on several projects to create a better admin user experience. Vuetify is layered on top and baked into WordPress themes and plugins.
You will need to add a little custom CSS to stop WordPress from stomping on the UX. You’ll also add a small localize script to seed Vue with relevant data from WordPress. A little REST applet to serve Vue requests and you get a fast good looking responsive app with far less effort than custom code, WordPress skeleton apps, React, or Angular.
Vue + Vuetify is my new go-to tool for plugins and themes. I am happier with my choice knowing that was created and is supported by small independent developers.
As PHP continues its march into the future with improved support for objects, better memory management, and notable performance boosts WordPress seems to be dead-set in sticking to the “must support old technology no matter how bad it is”. As of this writing, on the verge of the much-anticipated WordPress 5.0 release with the almost-modern reactive components interface — the past continues to hamper the technology by insisting on clinging to PHP 5.2 as the baseline version that plugins and themes should support.
PHP 5.2 Is Dead
Not recently dead. Long deceased. PHP 5.2 support officially ended OVER SEVEN YEARS AGO in January of 2011. That is about 3,000 years ago in human-time.
Far too often people do NOT ask me, or my colleagues in the industry, whom they should use as a web hosting company. Most business owners figure they are smart enough to at least select a host — especially when it comes to hosting a WordPress site.
And they Google it.
From the instant they made that decision they are screwed. Web hosting is an insanely profitable business and as such it has attracted tech titans; companies with a couple zeros in the “millions column” on their revenue sheets. They earn millions every month in hosting fees and pay a LOT of money to be the “first recommended” by Google or others.
WordPress REST performance sucks. There, I said it. Not because I dislike WordPress — in fact I think it is the best open source web application we have seen thus far. It is a great piece of technology. It even has the potential to be a great web application framework — in fact I use it for the Store Locator Plus managed service, MySLP.
However, unless you are in 100% complete control of every component in the system you are going to very likely end up with an underperforming over-burdened web service if you build your tech on typical WordPress components. Even the highly customized MySLP service is 5-10x slower than it would be if it was build on a completely customized application stack outside of WordPress.
WordPress is NOT built around performance. WordPress is built on two core tenets – ALWAYS support legacy users at all costs. Be extensible.