Obviously everyone else just wants to make sure their tool continues to be useful.
This is the only point of a Wiki, to be useful to as many people as possible.
That's definitely not the only point of Wikis.
Oh? What else could possibly be the value in a Wiki except to be useful? Abstract art?
Yes, the current software IS fine, because it works. That's my one request for the new Wiki, that it works. Workarounds are better than being non-functional. As such, it'd be really nice if you got it working before running a conversion, and leave the old stuff up until such point that the new stuff can meet the same standards the old stuff can meet. You both (Emi and Locriani) have stated that it should work fine for the latest IE eventually, so just don't set it as the primary system until it functions as well as what is currently used.
Actually, no, the current wiki does NOT work. I spend countless hours on maintenance for the current wiki to prevent it from exploding like a bomb and just flat out failing. If I were to leave on vacation for a week, the wiki would end up being down for 4 days. Do you consider that functional?
We have already stated that we're not going to switch to the new system until it is functional. All the issues you are raising have been addressed, and the issues you are raising are not actually contributing anything to this discussion. We opened this thread so we can get feedback on desired ancillary features for the new wiki.
I'm not interested in further debate on the merits of IE or IE support, especially as we've already stated we will be getting around to it. If you are worried about this, I invite you to contribute some code to the project instead of words to this thread--the former will actually accomplish something useful, the latter will only take developer time away from programming while we answer your questions.