This post examines what options one has for handling footnotes and references in HTML. It then presents a library that helps you with handling them.

Update 2011-12-07: Added case 5 and a conclusion.

Short answer: never. This post looks at five possible exemptions from the rule to always use === and explains why they aren’t.

Update 2013-04-09: now simulates the approach of the ECMAScript 6 specification draft (search for "HomeObject" to find the relevant parts).

This post examines how super-references work in JavaScript and how they will be simplified by ECMAScript 6. To understand this post, it helps to be familiar with JavaScript inheritance. If you are not, consult [2].

Whenever one specifies values for all directions in a single CSS property, one has to adhere to the standard order: top comes first, right second, bottom third, and left fourth. This post mentions three mnemonics for remembering that order.

Node.js version 0.6.3 (stable) came out on 2011-11-25. Highlight (quoting “Node v0.6.3” by piscisaureus for node blog):

Quoting “A game changer for interactive performance” by Vyacheslav Egorov and Erik Corry for The Chromium Blog:

Starting with version 8, Firefox supports HTML5 context menus. This post is a summary of “HTML5 context menus in Firefox (Screencast and Code)” by Chris Heilmann for Mozilla Hacks.

“Type Inference brings JS improvements to Firefox Beta” by Brian Hackett:

This post explains what named parameters are, how they can be simulated in JavaScript, and what improvements ECMAScript 6 will bring. Obviously, what is said about methods here applies to functions, as well.

I recently held a talk on JavaScript inheritance for a MunichJS meetup at Google Munich. Courtesy of TNG, a video has been recorded which I have uploaded to Vimeo.