Okay, I’ve tried it prop­erly now. It sucks. Sure, it’s prob­a­bly more usable for someone-who-really–should–be-using-WordPress.com-or-Blogger-or-Spaces or some­thing, but not for any­one who’s self-hosting. Its WYSIWYG edi­tor is doing a grave dis­ser­vice to the web as a whole, the default theme, Kubrick, is a seman­tic thing-of-nightmares, and its AJAX admin­is­tra­tion inter­face fails to degrade fairly com­pre­hen­sively. Yuck.

I’m using it now because I want to put some­thing quick and dirty together, but there’s no way I’m seri­ously con­sid­er­ing chang­ing any­thing else to Word­Press 2.0.x, nor, in the future, will I con­sider build­ing other sites around it. There’s one blog-only site (this is unusual: we’re not that groovy and Web 2.0 — RSS feeds seem to be an uphill bat­tle!) we’re going to do this week at work: that can be my ini­tial foray into TextPat­tern.

From there, who knows (Who knows all). If I don’t like it/it’s not flex­i­ble enough (For­tu­nately, Word­Press is rather flex­i­ble. I’m not stuck with it’s crap­pi­ness, I’d just pre­fer not to have to deal with it in the first place.), it’s prob­a­bly back to the land of roll-your-own solu­tions again. There are a few decent-looking Rails-esque frame­works for PHP float­ing about out there at the minute, so I might try using one of those. Appar­ently Rails/Ruby is ridicu­lously slow com­pared to PHP, so I’d rather not use it and really like it and be trapped in this frame­work that’s very Web 2.0, very expend­able, and very crap.

Can you tell I’m embit­tered with web (2.0) prod­ucts at the minute?