Hi. I have to agree with Stefan. It may seem like micro-optimizations should be the job of the Javascript engine, not that of the app code/programmer, but isn't. Thing is, such micro-optimizations like the ones described by Stefan are in most cases related to programmer intent, not just to implementation, and no Javascript engine can discover what a programmer was thinking (or not :D) when writing a loop or creating a data structure.
One more reason why the framework code should be optimized: qooxdoo, while being an excellent framework, is essentially used to create user interface. You can't really efficiently perform operations affecting half the databse using qooxdoo - you don't want to transfer that much of the database to the client. As such, most time spent by a qooxdoo application is in framework code. So the framework's efficiency is what determines overall speed. As such, speeding up the framework pays off, in that it speeds up most other applications significantly. Not that I don't understand the time and resources constraints placed upon the qooxdoo team (which I expect to get worse as html 5 takes off and receives massive browser support). br, flj ------------------------------------------------------------------------------ Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
