Pretty often, I see Wordfast Pro (3.4.2) freeze on pressing Alt+down (next segment),
obviously due to connection time with Microsoft Translator database server.
This delay is most likely needed for censorship authorities in your country to check the segments you are sending to Microsoft (and/or receiving from them) don't contain anything subversive...
But during that waiting time, I could have typed in my own input.
I mean, could it just not freeze? When human is faster than machine database, why not allow the translator to put in translation at the same time. And when the query result from database servers does come, just insert it right after .
Yes, what you would need is a multithreaded program in which querying MT services like Microsoft Translator etc. occurs in one thread, and entering translations in the editor occurs in another thread. Simple enough from a user's point of view, but much trickier for the programmers who need to implement this.
Querying MT in Wordfast Pro is treated like querying a TM, something that normally occurs in a fraction of a second, or 2-3 seconds at most (eg. remote TM). In my experience, querying Microsoft Translator is very fast, and so is querying Google Translate. Therefore it probably doesn't make much sense for Wordfast to implement multithreading, just because governments in some countries make things slower with their censorship efforts.