Most people that start off blogging seem to arbitrarily choose whatever solution they trip across first, or whichever one seems like the least work. I actually started a “home-grown” solution via Flash and XML, which worked fine after I figured out some of Flash’s XML-reading quirks, but it wasn’t a very advanced application from a point of view of functionality. (Text plus optional pic, tied to date.) When I decided to stop producing a static site in favour of a blog, I created some accounts in LiveJournal and Blogger, but gave them up because customisability didn’t seem to be encouraged (or easy to achieve). Even managed to install and try MoveableType as well, just before the big 3.0 license fiasco, and while I did like it, I was a little frightened off by the community “retaliation” happening because of 3.0. WordPress was next in line, and I loved it. Easy install, easy (well, relatively easy) customisation, plenty of great templates, and a vibrant community effort behind it. It took less than two days to produce basically everything that would form a million monkeys typing.
Now, there’s a new entry over at dsandler.org: The past and future of dsandler.org. (Or, how I learned to stop worrying and love WordPress.) He goes over the multiple solutions he examined before finally choosing WordPress:
And damn if it doesn’t work. From a features standpoint, WP includes fifteen different kitchen sinks, but the administrative UI is totally manageable (and the template functions are reasonable, if not always totally consistent) . The third-party developer community is active and prolific, and I quickly found an implementation of almost every feature I had imagined for the site (including next-day/previous-day links). And after a little time with the PHP code, I became pretty comfortable that I’d be able to hack together whatever I needed if I couldn’t find it elsewhere.