The first thing to do is to determine *why* the app is slower than you
would like; then you can direct your optimization efforts
appropriately. "What if" optimization (guessing at what's slowing
things down and then fixing those things) tends to be a time-waster.
tools and use those. I'd be interested to know what tools people on
app yet... Firebug (http://www.getfirebug.com) certainly offers some
nifty profiling features.
As for the question about the script parsing, well, it's easy enough
to find out. Disable all of the script stuff but leave the script in,
get some timings, then remove the link to the script. :)
Hope this helps,
tj / crowder software / com
On Mar 9, 9:53 am, Thierry <[EMAIL PROTECTED]> wrote:
> Im trying to improve the speed of a js app. After reading some
> articles i'm considering a few things.
> - Does it make sense to replace binding events with the old fashioned
> performance hit from parsing the script; and how large is this effect
> Tips and links regarding articles on js performance would be
> appreciated :)
You received this message because you are subscribed to the Google Groups
"Prototype: Core" group.
To post to this group, send email to email@example.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at