While I agree on the sub par javascript performance of IE forcing users to switch browsers isn't a valid solution in many professional situations.
Depending on what your trying to accomplish determines where your going to find the best bang for buck. In my experience the best way to increase performance is to reduce the amount of data your storing in the browser (I mean, don't store any giant lists like 500 index objects, make sure all references to Widgets are removed when your done with them, etc) - the larger IE memory the worse the performance. Reduce redundant calculations. Maybe even some refactoring into some design patterns might help. Maybe try posting some code or design areas you think are bottlenecking your app. On Oct 6, 1:07 pm, "Martin.Trummer" <[email protected]> wrote: > That's because the JS-engines of IE browsers > are shi... si.. suboptimal. > > try this js-performance test on different browsers, to see what I mean > (also try > chrome)http://wd-testnet.world-direct.at/mozilla/dhtml/funo/jsTimeTest.htm > > The only thing that may come to our rescue is google-chrome > framehttp://code.google.com/intl/en-EN/chrome/chromeframe/ > > On Oct 6, 12:03 pm, pal <[email protected]> wrote: > > > > > We have developed a stand alone web based application using GWT and > > performance of this application (Page Load time) in Mozilla firefox > > browser is 3 times better than the IE browser. Any help in improving > > performance of this application in IE browser would be great help to > > us. > > > Thanks, > > Pal --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en -~----------~----~----~----~------~----~------~--~---
