Except that my web server already has ASP.net. I get a few hundred hits a day. What do I care? :-) I understand what motivates someone like Dave to make it just require FTP and no active server components. He has a monetary interest in working with the largest crowd possible. Personally, I don't have any such need. I'd rather prefer something powerful and dynamic over something static and flaky, but that's just me. :-) [The .NET Guy]
Exactly! Let me burn cycles on my server - it has plenty to spare. :-) As to Drew's later point about caching and page regeneration, I actually don't care too much about complex caching and page generation algorithms for this application. If I have to re-generate a page every time I get a request, that's ok with me, assuming we're not talking about a huge amount of CPU time (which we shouldn't be). I'm also willing to have to tweak .aspx files and/or code to customize my site (theme, page layout, etc.), rather than have a complete customization engine...[Greg Reinacker's Weblog]
There sure is a lot of talk about a .NET weblog tool. I suppose I really should get metaBlog finished. Speaking which, I still don't know about the name, but I just can't think of anything else at the moment.