Thanks for info, Matt. At least we see someone is listening and VMware is aware of the situation, working on solution. Too late imho, but better late then never...
I do not want to mix into your business, but if (as you wrote) VMware is trying a) to extend C#-client life, b) to improve performance & usability of current web-client and c) to develop (I hope!) new html5-based client, you are terribly splitting your dev-resources. Maybe it would be better to skip "b". Just to fix C#-client asap so that it can do everything what current web-client can (except freezing, crashing, etc), then to concentrate fully on developing "next-gen" (maybe html5-based) client.
I mean, forget current flash-based web-client. It is not worth the effort. Even if you improve it, who is going to use it? And for how long? I see it in my everyday life: more and more of my business-partners strictly forbid any flash on corporate-network. No exception, not even for ESXi, period. Some of them even moved to different hypervisor, just because of this (and if they accepted those extra costs, they will probably never move back to ESXi). You know it is happening, and it should fire alarm in VMware-headquarters (if it is not already ringing).
I remember reading somewhere 2014 being called "the year when flash died". The clock is running, so you'd better have something ready ASAP. I personally could live for year or two with C#-client (with added functionality which I'm terribly missing). But I'm pretty sure I will not be able to manage ESXi-servers with your flash-based web-client for year or two even if web-client was much faster...
