WordPress 2 is horrible
05 Feb 2006Okay, I’ve tried it properly now. It sucks. Sure, it’s probably more usable for someone-who-really-should-be-using-WordPress.com-or-Blogger-or-Spaces or something, but not for anyone who’s self-hosting. Its WYSIWYG editor is doing a grave disservice to the web as a whole, the default theme, Kubrick, is a semantic thing-of-nightmares, and its AJAX administration interface fails to degrade fairly comprehensively. Yuck.
I’m using it now because I want to put something quick and dirty together, but there’s no way I’m seriously considering changing anything else to WordPress 2.0.x, nor, in the future, will I consider building 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 battle!) we’re going to do this week at work: that can be my initial foray into TextPattern.
From there, who knows (Who knows all). If I don’t like it/it’s not flexible enough (Fortunately, WordPress is rather flexible. I’m not stuck with it’s crappiness, I’d just prefer not to have to deal with it in the first place.), it’s probably back to the land of roll-your-own solutions again. There are a few decent-looking Rails-esque frameworks for PHP floating about out there at the minute, so I might try using one of those. Apparently Rails/Ruby is ridiculously slow compared to PHP, so I’d rather not use it and really like it and be trapped in this framework that’s very Web 2.0, very expendable, and very crap.
Can you tell I’m embittered with web (2.0) products at the minute?