Backbone Koans: Learn Backbone by Fixing Unit Tests #javascript http://t.co/6sOCQzem

Windows and Node: Writing Portable Code by @dailyjs #javascript http://t.co/81hVY1BV

Windows and Node: Writing Portable Code by @dailyjs #javascript

javascript strict mode

Test your code! Unit testing in #JavaScript with jQuery, QUnit, & Mockjax http://t.co/eNntMinf

Test your code! Unit testing in #JavaScript with jQuery, QUnit, & Mockjax

Working with files in #JavaScript, Part 1 by @slicknet http://t.co/i56f27bc

Working with files in #JavaScript, Part 1 by @slicknet

[free webcast]: Know Your Engines: How to Make Your #JavaScript Fast http://t.co/bsP5fFjJ //Tomorrow

[free webcast]: Know Your Engines: How to Make Your #JavaScript Fast //Tomorrow

Not to be hyperbolic, but the continual promotion of the "module" pattern in JavaScript is some of the worst advice you can give.
JavaScript has prototypes for a reason -- use them. By using the "module" pattern to build objects, you create a separate copy of every function for every instance of every object you create. If you're just creating a handful of objects, it's no big deal, but if you're creating a large number of objects, it's horribly CPU and memory inefficient.
Modern JS runtimes like Chrome/V8 can create and store a million small objects with prototypes and "new" in a couple seconds, using just a dozen or so megabytes of RAM. Creating the same million small objects with the "module" pattern takes minutes, uses many hundreds of megabytes of memory, and often crashes the browser.
And that's just the pragmatics -- there are deeper semantic reasons to use real prototypes.

.bind('ajax:beforeSend', function(xhr, settings) {})
 .bind('ajax:success',    function(data, status, xhr) {})
 .bind('ajax:complete', function(xhr, status) {})
 .bind('ajax:error', function(xhr, status, error) {})

Note to aspiring Node developers: learn more JavaScript. Specifically, stuff like this: #no...