let me summarize this discussion: 1. TaskSpeed is not relevant benchmark for this topic. I'm talking about speed of qooxdoo and not some css selector stuff which is irrelevant. The speed killer is count of needed DOM elements per application/widget, not javascript size or css selector speed.
Just look how many DOM elements are created for simple button, this is really not about selectors. 2. Qooxdoo will be never for classic web-apps for speed/size reasons. I can accept that, but the qooxdoo community have to accept that qooxdoo will never spread (for me this is not problem at all). 3. I will never post here another qooxdoo critique mail. I have feeling that critique is not welcome here and I really tried to be as objective as possible. I can understand that qooxdoo can't be good for everything, but really think that the performance should be improved, this is all I wanted to say... Best regards Petr ------------------------------------------------------------------------------ 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
