Subscribe to my Feed, follow me on Twitter, recommend me on Working With Rails or see my code on GitHub
Comment
You're viewing a comment to the post Optimising by cheating - how to trick your users into thinking your site is fast
Subscribe to my Feed, follow me on Twitter, recommend me on Working With Rails or see my code on GitHub
You're viewing a comment to the post Optimising by cheating - how to trick your users into thinking your site is fast
They're justified and they're ancient, and they drive an ice-cream van
By Christian at Tue 10 Feb 09:14
Interesting read! In your example I guess you could also slim down the initialization and then do all the expensive stuff for a single element the first time the user tries to drag something.
Using a loader will probably make 20ms a fair wait. The upside of this is that you’ll probably never have to make everything draggable, thus saving some potential memory loss (unless you somewhere free up this.element = el)
On another point: you should use the syntax highlighting at all times, not just mouseover, makes the easier to read.