Martin, didn't know taskspeed; it is quite impressing. Qooxdoo really performs well; I wonder if 1.2 SDK performance can match?
Petr, when first time participating in a qooxdoo project some three years ago (qx 0.6.6), there actually *was* a performance issue, but it was clearly limited to the actual customer using IE6 (IE6 must die!). We made a bunch of efforts to get the most of it (layout optimization, compression of the script files, etc.), but a bad browser is a bad browser. Time went by, and my customers now use IE7+; I'm supporting some elderish HTML web apps (pre AJAX), where I don't make use of qooxdoo, and I don't plan to even when enhancing these apps. But any *new* project where I am free to decide the technique, qooxdoo is my only choice. I don't even need to invest time to learn zillions of other JS frameworks, because I know qooxdoo can offer all I need. Still speed remains king, and as long as one browser does a better jit job than the other, I prefer a focus on speed optimization over feature enhancements. So to answer your questions in short: 1. no 2. no 3. yes 4. no Greetings, Stefan On 30.08.2010 16:59, Martin Wittemann wrote: > Hi Petr, > >> 1. Is qooxdoo slow? > http://dante.dojotoolkit.org/taskspeed/ > Ever heard of that? ------------------------------------------------------------------------------ This SF.net Dev2Dev email is sponsored by: Show off your parallel programming skills. Enter the Intel(R) Threading Challenge 2010. http://p.sf.net/sfu/intel-thread-sfd _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
