Hi devs, I know that the title is gutter, maybe everybody know about that, but qooxdoo is probably the slowest javascript framework available. When I started working with qooxdoo 0.7, I feel that it is slow (and not only me, this mark was also from other js framework forums - ExtJS for example). At that time there were plans for qooxdoo 0.8 that said that it will be faster, less DOM elements will be needed for GUI and architecture will be cleaner.
I think that only the 'architecture' goal was finished. The number of DOM elements needed for equal application to 0.7 version is higher and this means that also browser performance will be worse. My experiences are showing that number of javascript code is not problem. Browsers are using JIT compilation and other very interesting tricks to make js working as fast as possible, but problem will be always DOM - It's hierarchic structure and each element is VISIBLE. If you don't believe me, try very simple task - Try to write efficient AABB collision detection in C/C++ (each browser need it to be efficient in DOM). In small qooxdoo app it's not a problem (1000 divs are acceptable), but imagine larger application with tens of tabs - you simply get DOM hierarchy which have 10000 or more elements, and this can't be never fast. I have not calculated how many DIVs are needed for one widget, but I think that 5 are maximum for efficient framework. Now I'd like to write why this is getting to be a problem for me. I'm using qooxdoo about 2 years and I learned to do some things with it. The object model is nice, widgets are good designed and I'd like to use similar model in classic web-pages. But I can't. The qooxdoo code is huge, speed is unacceptable and using generator to minimize js code is not possible (I can't imagine using this tool for web-pages). So I'm using different frameworks for web-pages and web-apps. Okay, I do not need super rich functionality in web-pages, but it's time consuming to work with different tools for the same runtime environment. What about other developers? 1. Is qooxdoo slow? 2. Is qooxdoo tooling uncomfortable for you? 3. Are you prefer improving the speed over features at this time (mature, version 1.2, 1.3)? 4. Do you using qooxdoo for classic web-pages (to add some rich functionality)? Best regards Petr Kobalicek ------------------------------------------------------------------------------ Sell apps to millions through the Intel(R) Atom(Tm) Developer Program Be part of this innovative community and reach millions of netbook users worldwide. Take advantage of special opportunities to increase revenue and speed time-to-market. Join now, and jumpstart your future. http://p.sf.net/sfu/intel-atom-d2d _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
