High-Performance javascript: Why Everything You’ve Been Taught is Wrong

Please enabled JavaScript and install Flash Player 8 or above for view the content.
Created on 31 August, 2007by osnow

Share

URL:
Embed:

Additional Info

Language: English Status: Public Category: Software Creative Commons: Attribution-NonCommercial-ShareAlike License
Views: 4,563 | Comments: 1 | Favorited: 0 | Rating: 1 Login to rate
Add to Favorite SaveCancelSaved
Please enter the folder name:
Speaker: Joseph Smarr
Company/Organization: Plaxo, Inc.
In sum, Joseph argues for a four-point approach to achieving maximum performance in your web-app:
  • Be lazy: Don’t load or do things before you need to; maybe you won’t need to load or do them at all.
  • Be responsive: Make things happen quickly. If you can shave 100ms off of an interaction by responding to a mousedown event instead of a click event, do it.
  • Be pragmatic: Frontend engineering is hard enough. Don’t make it harder than it needs to be.
  • Be vigilant: Blank web pages are fast. Web pages become slow because you put stuff in them; slowness is your resonsibility. Vigilance is required to prevent slowness.

http://josephsmarr.com/2007/08/29/my-ajax-talk-is-now-on-yui-theater/

Comments

useruseruser 13 February, 2008 09:11
For accessibility, onmousedown needs to be paired with onkeydown to accommodate keyboard navigators. Otherwise, it's better to stick with onclick, which most agents automatically associate with the enter key onkeypress. Safest: Use device-independent events (onfocus, onblur, onchange) or pair events (onmousedown onkeydown or onclick onkeypress).
 

Post Comment

You want to comment?
Join VCASMO for a free account, or Login if you are already a member.

Clear Trace