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 tried the freeway, they tried the highway, they tried any which way, and they were taken down!
By Tore Darell at Tue 10 Feb 15:10
Christian: I hadn’t thought of that, and it seems like it would work very well. The user probably isn’t going to notice those ~30ms between clicking the element and starting to drag it. It seems there are a lot of ways to optimise JavaScript performance that have to be applied wherever they make sense. I’m sometimes torn between doing things the “right” (i.e. maintainable) way and the faster way, but I guess in the end, once you get over a certain threshold, performance wins.
You’re right about the syntax highlighting too – I thought I was being clever, but it turns out it’s just annoying :)
Luke: I was actually using YUI3 on this project, which (I think) expects to be loaded right before </body>, and it does indeed help a lot. But the browser was still waiting to render the rest of the page, which I think was caused by me adding some class names to the elements. It seems that once the JS engine gets a hold of the reins it doesn’t give them up until it’s done..