ivtch,
Since you have asked for my opionion, here it is:
It would be extremely wrong of me to set an expectation in this case.
It should also be noted that the Blog Module, whether or not it COULD ultimately support your use-case, was not built with that intent in mind.
The Blog module was never intended to become a "Blogger or WordPress" service. If it were, if would have been architected much differently, for instance, the blog entries might have been generated as static HTML instead of serving them at each incoming request by querying the database.
That said, internet applications (such as DotNetNuke) run by virtue of "live" data, so there should be no reason why the blog would not satisfy your use-case, provided it is backed-up by a solid backend infrastructure and set-up.
In addition to the above mentioned, DotNetNuke affords you the choice of OpenSource. This means that IF and WHEN one such products does not meet your requirements, you can easily donwload the code and modify it to your heart's content. Blogger, WordPress and the likes do not provide you with such flexibility.
You should also know that we are soon embarking in the development of the Next Generation Blog Module (a whole re-write) and would love to see your use cases and derive from them a list of task items that I would be happy to include in the road map.
I hope that this answers your questions and mitigates your concerns.
Thank you for Nuking!