On 08/31/10 14:12, Martin Wittemann wrote:
> Just a little side note and a reminder for all who haven't seen it.
> http://gmx.com/ is one of our products we develop here at 1&1 which is
> pretty huge and still fast. The guys at the development team did a
> good job recently in speeding up the initial startup. Take a look and
> tell me if you still think its slow. But keep in mind that this app
> has about as much code as the whole qooxdoo framework.
> Additionally, qooxdoo is used alot in traditional web pages at 1&1. So
> if a company can rely on it, why should it not be mature enough? See
> for example this site: http://www.1und1.info/xml/order/CloudDynamicServer
>
>
hi martin,
maybe qooxdoo documentation about performance could be improved. for
example, i noticed that gmx.com has optimized code specific to the
client browser. i didn't know that the generator could do that.
e.g.
http://www.gmx.com/client/static/script/compiled-gecko-6.20.16.0.js
http://www.gmx.com/client/static/script/compiled-webkit-6.20.16.0.js
http://www.gmx.com/client/static/script/compiled-opera-6.20.16.0.js
i'm sure they'd have lots of other tips about qooxdoo performance. maybe
just publish an interview with them :)
also, maybe a small demo about instance pooling would be nice. something
like: http://bit.ly/8YXfpz
btw, http://demo.qooxdoo.org/current/apiviewer/#qx.util.ObjectPool
"""
... used to pool instances of any type of Object (expect singletons).
"""
should be except.
best regards,
burak
<http://www.gmx.com/client/static/script/compiled-webkit-6.20.16.0.js>
------------------------------------------------------------------------------
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
