david-mcneil

;; Define a "base type" of Dog
(defrecord Dog [breed])

;; Define a "sub type" of TrainedDog
(defrecord TrainedDog [dog word])

;; The interface that both Dog and TrainedDog will implement
(defprotocol Talker
  (bark [_])
  (speak [_])

DanHulton

# Swappable Mixins in CoffeeScript
# ================================

# Many thanks to Hashmal, who wrote this to start.
# https://gist.github.com/803816/aceed8fc57188c3a19ce2eccdb25acb64f2be94e

# Usage
# -----

# class Derp extends Mixin

dandean

/**
 * Monkey patch `Backbone.Model.extend()` with ES5 getters/setters for each
 * attribute defined in the defaults. Gives you the added bonus of being
 * to pass your backbone models directly to your Mustache.js views.
 *
 * Example:
 *
 * var User = Backbone.Model.extend({
 *   defaults: {
 *     username: undefined,

caseyohara

# A list of possible usernames to reserve to avoid
# vanity URL collision with resource paths

# It is a merged list of the recommendations from this Quora discussion:
# http://www.quora.com/How-do-sites-prevent-vanity-URLs-from-colliding-with-future-features

# Country TLDs found here:
# http://en.wikipedia.org/wiki/List_of_Internet_top-level_domains#Country_code_top-level_domains

# Languages found here:

paulirish

// http://paulirish.com/2011/requestanimationframe-for-smart-animating/
// http://my.opera.com/emoller/blog/2011/12/20/requestanimationframe-for-smart-er-animating

// requestAnimationFrame polyfill by Erik Möller. fixes from Paul Irish and Tino Zijdel

// MIT license

(function() {
    var lastTime = 0;
    var vendors = ['ms', 'moz', 'webkit', 'o'];

alexaivars

Function::define = (prop, desc) ->
    Object.defineProperty this.prototype, prop, desc

class GetterSetterTest
    constructor: (@_obj = {}) ->

    # 'obj' is defined via the prototype, the definition proxied through
    # to 'Object.defineProperty' via a function called 'define' providing
    # some nice syntactic sugar.  Remember, the value of '@' is
    # GetterSetterTest itself when used in the body of it's class definition.

tuzz

/*
Copyright (c) 2017 Chris Patuzzo
https://twitter.com/chrispatuzzo

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

davepeck

Function::property = (prop, desc) ->
    Object.defineProperty this.prototype, prop, desc

class Foo
  @property 'neat'
    get: ->
      42

class Bar extends Foo
  @property 'neat'

jamarparris

The MIT License (MIT)
Copyright (c) 2013 Jamar Parris

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE S

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