Well, it’s been common knowledge for a while now but the launch of WordPress 2.0 aka Duke has now been officially announced on the main WP development blog.
As someone who’s a longtime WP user, a diligent upgrader, subscribed to the various WP dev mailing lists, played around with the latest SVN codeset, and helps out from from time to time on the WP support forum, you’d probably be expecting that I would have been first in line to upgrade. If that was the case, then you’d be wrong. So, why am I not upgrading?
Asking the wrong question
Owen’s asked a fair question; why aren’t more people upgrading? Judging by the response that he’s received thus far, a lot of the concerns are in regards to the upgrade process and concerns about plugin incompatibility. There are concerns about the stability of the rushed release and the lack of official announcements hasn’t helped.
All of these are quite correct and go someway towards answering Owen’s query. However, in my case, personally speaking, things are a lot simpler. It’s not so much why aren’t I upgrading but why should I upgrade?
What’s in it for me?
First off, to stem off the immediate counter-responses, I’m fully aware what’s new and improved in WP 2.0. This is not about that; in fact, if I was setting up a new blog, I’d easily choose WP2.0. Wait a minute, I did
The problem is that when it comes to upgrading a blog, there is some thought required. I have to mentally weigh up the benefits of upgrading against the cost of upgrading. Is this worth the effort, the time and the hassle? Even if there were no plugin incompatibilities, even if the new release didn’t have any new bugs or issues, I would still have to decide whether or not I would sufficiently benefit from this release.
OK, let’s have a look, shall we?
The rich text WYSIWYG editor
I can see how this would be useful for many and tinymce is a fine choice. And whilst some would consider such to be bulk, it doesn’t really bother me. It’s not perfect and it’s not for me, but it’s optional so I turn it off. Since I don’t care in the least about it being there however, that means that, by definition, it’s also not a compelling reason for me to upgrade.
Admin Redesign and sprinkings of AJAX
Ahh, so it’s no longer plain and minimal. Some of the work done with the Shuttle project has made it’s way into the WP core. However, with the advent of Tiger Admin plugin, it’s a case of too little, too late. Whilst Steve’s plugin is generally cosmetic and the admin overhaul is much more than that, there’s not really enough there to act as a deal breaker for me.
Ping Delay Removed, Improved Post Preview, New Built-In Plugins
Nice? Yes. Killer features? Well, not quite.
The ping delay was annoying but I’ve dealt with it and moved on. Besides, that little delay gives me a few seconds thinking/tab switching time. The post preview is quite handy, but once again, I’ve learnt to live without it quite comfortably. The bundled plugins? DB-backup is very useful but I’ve had it installed for a while now. Akismet? Spam is managable at present with Bad Behaviour and other measures. Should situations change, I’m smart enough to try it out.
Oh how I wish this site was popular enough that this mattered.
Me use, me like, …but not enough.
New Import System, User Roles and Capabilities, User Metadata, Presentation Page Changes
Another case of the wrong audience scenario. No need to import, no need to support multiple users. That said, I’m fully behind these improvements and will prove handy for new sites but the question was why upgrade, so the answer unfortunately is once again, meh.
All good choices and once again, all totally irrelevant when it comes to convincing me to upgrade. The last two will be handy for subsequent upgrades and future work, but it’s all about the present. Nothing here for today.
Now that I’ve said my piece, my question for Owen, Matt et al is: why should I upgrade? Convince me, because I’ve been playing and using WP 2.0 for a while now and I just don’t see enough reasons there as yet. Looking forward to 2.1 and beyond