samnang

# Install Bash 4 using homebrew
brew install bash

# Or build it from source...
curl -O http://ftp.gnu.org/gnu/bash/bash-4.2.tar.gz
tar xzf bash-4.2.tar.gz
cd bash-4.2
./configure --prefix=/usr/local/bin && make && sudo make install

# Add the new shell to the list of legit shells

donnut

"add this to .vimrc
source ~/dev/jasmine2qUnit/jasmine2qUnit.vim
nmap ;q :call ConvertJasmineTest2qUnit()<CR>

utsengar

/*
 * This decorates Handlebars.js with the ability to load
 * templates from an external source, with light caching.
 * 
 * To render a template, pass a closure that will receive the 
 * template as a function parameter, eg, 
 *   T.render('templateName', function(t) {
 *       $('#somediv').html( t() );
 *   });
 * Source: https://github.com/wycats/handlebars.js/issues/82

sjl

var empty_list = function(selector) {
    return selector(undefined, undefined, true);
};

var prepend = function(el, list) {
    return function(selector) {
        return selector(el, list, false);
    };
};
var head = function(list) {

jed

How to set up stress-free SSL on an OS X development machine

One of the best ways to reduce complexity (read: stress) in web development is to minimize the differences between your development and production environments. After being frustrated by attempts to unify the approach to SSL on my local machine and in production, I searched for a workflow that would make the protocol invisible to me between all environments.

Most workflows make the following compromises:

• Use HTTPS in production but HTTP locally. This is annoying because it makes the environments inconsistent, and the protocol choices leak up into the stack. For example, your web application needs to understand the underlying protocol when using the secure flag for cookies. If you don't get this right, your HTTP development server won't be able to read the cookies it writes, or worse, your HTTPS production server could pass sensitive cookies over an insecure connection.

• Use production SSL certificates locally. This is annoying

thomasboyt

/* jshint node: true */

module.exports = function(grunt) {
  require('load-grunt-tasks')(grunt);

  grunt.initConfig({
    transpile: {
      main: {
        type: 'amd',
        moduleName: function(path) {

alanpeabody

{
  "app/models/*.js": {
    "command": "model",
    "template": [ "export default DS.Model.extend({", "});" ]
  },
  "app/router.js": { "command": "router"},
  "app/routes/*.js": {
    "command": "route",
    "template": [ "export default Ember.Route.extend({", "});" ],
    "alternate": "app/controllers/%s.js"

coderberry

My Reading List

• 5 Minutes of JavaScript
• A Fresh Cup
• A MOMENT OF CEREBUS
• Coding Value Blog
• Comic Book Resources
• CSS-Tricks
• DailyJS
• Open Web Platform Daily Digest

dagda1

App.computed.union = function() {
  var args, options, properties;
  
  properties = a_slice.call(arguments);
  
  args = properties.map((function(_this) {
    return function(prop) {
      return "" + prop;
    };
  })(this));

staltz

The introduction to Reactive Programming you've been missing

(by @andrestaltz)

---

This tutorial as a series of videos

If you prefer to watch video tutorials with live-coding, then check out this series I recorded with the same contents as in this article: Egghead.io - Introduction to Reactive Programming.

---