All major browsers fire a "resize" event on the window object when the browser is resized. This can be extremely useful for managing complex layouts that might not be possible with pure CSS. The problem is that certain browsers fire multiple resize events while the user resizes the window. Generally, this is harmless or even desirable, but if you have to do expensive DOM manipulation on resize, then it becomes quite undesirable. Unfortunately, browsers do not implement a "resizestop" event - which would be handy. Thankfully, we can sort of emulate a "resizestop" event using JavaScript.
I recently wrote a small script for caching results of jQuery calls, which I've titled jQuery DOM Cache. It works just like jQuery proper in that you pass it a selector and it returns a collection of matching DOM elements. The difference is that it stores the result of each selector you pass it for recall later.
I recently recieved a Chrome OS Cr48 notebook through Google’s Pilot Program. If you’re at all interested in web technology, you’re probably aware of this program. In case you aren’t, I’ll give you the skinny before discussing the good and bad of Google’s first foray into hardware for cloud-based computing
While responsive web design with CSS media queries is rippling through the web design community, I question its practical use for business websites. Jason Grigsby has an excellent write-up of the technical reasons for skepticism, so I won't go into too much detail reiterating them.