Yes, this looks like another eruption of off-topic posts... IMHO, VB should
be ported because that is the only way to achieve portability for MS Office
documents. StarOffice is really cool but ultimately not feasible if you are
exchanging documents with a group of MS Office folks. Unfortunately, VB
would bring office products closer to managing that feasiblity.
Unfortunately, VB is not an elegant language but it suits it's purpose. Too
bad tcl, perl, python, java, or javascript wasn't used for building these
dynamic docs. But those languages present quite a learning curve, this was
VB strength. Also, it enabled MS to lock in a lot of folks to it's
proprietary ways of doing things.
