hi,
i think it would be fair to make a difference. i agree not to change the code to
be faster in some browsers (or JS engines). this reminds me on optimization
guides for java (1.0, 1.1). most of these tips were wrong when using java 1.3
and some of the tips were counterproductiv in later java versions (some of these
tips complicated the job for the jit).
so if the code is clear and correct: don't change it (it should be clear, that
dead-code or something incorretness should always be removed).
but: most of qx-people use the qx-generator and imho this is some sort of
compiler. and compiler can do optimizations. and they can and should do this
micro optimizations which should NOT be done manually in the code. so if this
generator/compiler can optimize loops to be perform a little faster ... why not?
yes i know: most of the JS-engines will do this in the future. but as stefan
said: this is future music. and if we have a IE9 or FF4 or chromium or ... it
will last a few more years until theses browsers are used by many people
(webhits says that 38% of the people use at least ie6!).
just my 2 cents ...
</usc>
ps: to be honest, i don't have any performance problem with qx and i also do not
use the "generator.py" so i am really the wrongest person to say somthing :-)
------------------------------------------------------------------------------
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
