Well, to be more precise, I strongly suspect they are still using the GWT -- which, being a Java-to-Javascript compiler, is pretty demanding of Javascript.
My suspicion, based on some of the nuances, is that it's a derivative of the original Wave client, not quite as performance-crushing as the original (eg, it has normal scrollbars instead of Wave's pointlessly idiosyncratic ones), but still extremely demanding.
And yes, IE8's Javascript performance is wretched. Nonetheless, most of our customers (large commercial banks), and therefore many of our internal users, still default to it. Pinning the ultimate blame on IE doesn't change the fact that, for a large number of users, this rules out the near-term use of the tool...
no subject
My suspicion, based on some of the nuances, is that it's a derivative of the original Wave client, not quite as performance-crushing as the original (eg, it has normal scrollbars instead of Wave's pointlessly idiosyncratic ones), but still extremely demanding.
And yes, IE8's Javascript performance is wretched. Nonetheless, most of our customers (large commercial banks), and therefore many of our internal users, still default to it. Pinning the ultimate blame on IE doesn't change the fact that, for a large number of users, this rules out the near-term use of the tool...