As with many static-blog compilers out there, I don't really have Chronicle figured out from a user perspective -- I run Ode, which isn't at all static but is coded in Perl and is fairly easy to get running on most shared hosts.
One of Chronicle's notable features is native comments. I don't know of many other flat-file (static or dynamic) blogging systems that don't rely on Disqus for commenting.
Aside from eliminating a task for developers, a big reason to use Disqus and not to code a native commenting system could be the spam problem. For that reason, Disqus might very well be the best solution out there. But I've seen many users of blogging software who are uncomfortable (or not comfortable) outsourcing their comments to a third-party site.
Steve Kemp has a whole site/service/program at BlogSpam.net that deals with the spam problem in blog comments. It's definitely worth a look, as is the whole of Chronicle.
However you look at it, the option to host your own comments is a good and viable one, as is the option to outsource them to Disqus or even Facebook, as Anil Dash does.
Note: While I remain interested in the landscape, if you will, of blogging software, I remain committed to Ode as my personal-blogging platform of choice, even as my "professional" life is all about WordPress. More on this in an Ode-focused post in the near future.
This is another one I’m going to look at.