elijahmanor

Animated Gifs

gist:4277230

// jQuery - failures persist along the chain
$.Deferred(function(d) { d.reject() })
    .then(function() { console.log("Success handler 1") }, function() { console.log("Fail handler 1") })
    .then(function() { console.log("Success handler 2") }, function() { console.log("Fail handler 2") });

// Output:
// Fail handler 1
// Fail handler 2

// ------------------------------------------------------------------------------------------------------

mockee

define('mod/bbsync', [
  'underscore'
, 'mod/ajax'
], function(_, Ajax) {
  function sync(method, model, options) {
    var url = model.url, data

    url = _.isFunction(url) ? model.url() : url
    data = method === 'create' || method === 'update'
      ? model.toJSON() : {}

Alligator

                                         JSWEEKLY BINGO
+-------------------------------+-------------------------------+-------------------------------+
|  An atricle from someone who  |                               |                               |
|        just figured out       |    Baby's first functional    |    How to do this one very    |
| prototype-based OO and thinks |          programming          |   specific thing in Node.js   |
|  everyone else needs telling  |                               |                               |
+-------------------------------+-------------------------------+-------------------------------+
|                               |                               |                               |
|     A new jQuery release      |    A job in San Francisco     |   An introduction to an MVC   |
|                               |                               |           framework           |

domenic

This article has been given a more permanent home on my blog. Also, since it was first written, the development of the Promises/A+ specification has made the original emphasis on Promises/A seem somewhat outdated.

You're Missing the Point of Promises

Promises are a software abstraction that makes working with asynchronous operations much more pleasant. In the most basic definition, your code will move from continuation-passing style:

getTweetsFor("domenic", function (err, results) {
 // the rest of your code goes here.

cowboy

var stringify = function(obj, prop) {
  var placeholder = '____PLACEHOLDER____';
  var fns = [];
  var json = JSON.stringify(obj, function(key, value) {
    if (typeof value === 'function') {
      fns.push(value);
      return placeholder;
    }
    return value;
  }, 2);

cowboy

var isPrimitive = function(val) {
  return val !== function() { return this; }.call(val);
};

eliperelman

Whitbeck’s Law

If it exists, there is a GIF of it.

Manor’s Law

For every message there is an equal and opposite deletion.

Cowart’s Law

All great messages will be deleted before you have a chance to read them.

Neiner’s Law

getify

// all this `toJSON()` does is filter out any circular refs. all other values/refs,
// it passes through untouched, so it should be totally safe. see the test examples.

// only extend the prototype if `toJSON` isn't yet defined
if (!Object.prototype.toJSON) {
	Object.prototype.toJSON = function() {
		function findCircularRef(obj) {
			for (var i=0; i<refs.length; i++) {
				if (refs[i] === obj) return true;
			}

jcreamer898

Using AmplifyJS with RequireJS 2.0

With the lastest version of Require, a new config object was introduced, the shim.

http://requirejs.org/docs/api.html#config-shim

That allows Amplify to now be used within AMD projects.

Have Fun!