Karl Martino's experiments with Movable Type continue. He says that Radio works the same way as MT, but with all due respect, I don't think that's true.
When I post something to my weblog, three files are updated, every time. 1. The weblog home page, 2. the archive for the day, and the 3. RSS feed. On my first post of a day, the calendars for every other day in the month are re-rendered and upstreamed.
Key point, and perhaps Karl doesn't know this (he's not using Radio after all), when I post something to my weblog, it takes me back to the editing page in less than two seconds, where I can edit my post or do another one. There's a link on the desktop website home page to the public (static) version. Unless there's a lot of congestion on the net, by the time I click on the Home link, the new version has already been upstreamed. I ususally can't get there before the update has happened.
There are fundamental differences between Movable Type and Radio, architectural ones, and tweaks. We optimized the user experience of Radio, ask the beta testers, it's documented on the Radio-Dev list. When Karl says it's all the same, I don't think he's right about that. Radio doesn't make the user wait while it does the work.
In any case, it's great that there are users checking out all the blogging products and writing about their experiences. This is one area the bloggers should be able to shine. Let's get more comparative reviews on the tradeoffs of various approaches. This way we can all learn more quickly, and the art of blogging software can advance. Thanks.