Having done both, repeatedly: use Wordpress or another blogging platform (I hear good things about Jekyll but haven't used it).
The feature set issue looks small, but becomes bigger the more time you spend on the single piece of blogging software. And the bigger and more sprawling your homebrew system becomes, the slower it is to add additional features, and the more likely you are to introduce bugs or security issues...
On that subject, security's another major problem. SEO comment spammers are persistent, and if they discover a way that your blogging code isn't secure, they'll hammer you. WP, provided you keep it up to date, has a lot more eyes making sure it's secure than you do.
(Counter-argument: if you're not going to keep the install up to date, don't go WP. You WILL get hacked.)
I tried jekyll and it is an excellent compromise, providing all the goodness of a flexible templating and layout system with the ease and server-lessness of static pages. Combined with s3-website, it took me about 3 hours to rebuild my blog (mostly time spent editing old posts into markdown).
The feature set issue looks small, but becomes bigger the more time you spend on the single piece of blogging software. And the bigger and more sprawling your homebrew system becomes, the slower it is to add additional features, and the more likely you are to introduce bugs or security issues...
On that subject, security's another major problem. SEO comment spammers are persistent, and if they discover a way that your blogging code isn't secure, they'll hammer you. WP, provided you keep it up to date, has a lot more eyes making sure it's secure than you do.
(Counter-argument: if you're not going to keep the install up to date, don't go WP. You WILL get hacked.)