Qard

{
  "start": "node --harmony server.js",
  "dev": "exec-parallel 'npm run watch' 'npm run watch:test' 'nodemon --harmony server.js'",
  "test": "mocha --harmony",
  "coverage": "npm run coverage:report",
  "coverage:build": "rm -rf coverage && node --harmony istanbul cover _mocha",
  "coverage:report": "npm run coverage:build && istanbul report",
  "coverage:html": "npm run coverage && node-open coverage/lcov-report/index.html",
  "build": "exec-parallel 'npm run build:js' 'npm run build:css'",
  "build:js": "browserify assets/js/main.js -o public/js/bundle.js",

Qard

var Emitter = require('events').EventEmitter
var evil = new Emitter

evil.on('foo', function (get) {
  console.log('privateThing is', get('privateThing'))
})

function foo () {
  var privateThing = 'secret'
  evil.emit('foo', function (prop) {

Qard

function times (n, fn) {
  return function () {
    if (n > 0) {
      n--
      return fn.apply(this, arguments)
    }
  }
}

var hello = times(2, function () {

Qard

require 'openssl'
require 'net/http'

uri = URI.parse("https://semver.io/node/versions")
# uri = URI.parse("https://semver.io/iojs/versions")
http = Net::HTTP.new(uri.host, uri.port)
http.use_ssl = true
http.verify_mode = OpenSSL::SSL::VERIFY_NONE # read into this
result = http.get(uri.request_uri)

Qard

Problems

• Input events are difficult/impossible to hook into at framework level
  • Angular uses html data-binding without user-defined interactions, or sometimes ng-click attributes (but still bound to a private scope). This logic is all lost somewhere deep in the internals, completely inaccessible to outside code.
  • Ember uses an action filter in mustache (http://emberjs.com/guides/templates/actions/). Again, inaccessible internals...
  • React uses on* attributes in JSX. It's possible to intercept them via React.createElement(...), but associating the virtual DOM representation with the corresponding real DOM element is not possible without patching the DOM itself.
• Scope inheritance in angular makes it impossible to know what controller a given thing in the scope is coming from without modifying the core itself. (https://docs.angularjs.org/guide/controller#scope-inheritance-example)
• MV* approach between the different frameworks varies rather drastically.
• Angular has controllers, but the

Qard

var algorithm = crypto.getHashes()[0]
var hash = crypto.createHash(algorithm) // crypto entry
hash.update('foo')
fs.readFile(__filename, function (err, data) {
  hash.update('bar')
  var hashed = hash.digest() // crypto exit
  done()
})

Qard

JSON.fstringify = function(object) {
	return JSON.stringify(object, function(key, value){
		if (typeof value == 'function') {
			return value.toString();
		}
		return value;
	});
};

Qard

function chainer(){
	var chain = [];
	function add(callback) { chain.push(callback); }
	function next() { if (chain.length) { chain[0](); chain.shift(); } }
	return { add: add, push: add, run: next, start: next, next: next };
}

// Make a new chain.
var chain = new chainer();

Qard

/**
 * Some basic rewriting to connect the functions via prototype.
 * It's faster that way as the functions are only addressed to memory once.
 * 
 * Also stores the canvas and context as instance properties rather than passing them through everything.
 * Again, it is faster that way.
 */

/**
 *

Qard

!function (Backbone) {
  // Store blank stuff here
  var blankEl = $()
    , blankModel = new Backbone.Model.extend()
    , blankCollection = new Backbone.Collection.extend({
      model: blankModel
    })
    , blankView = new Backbone.View.extend({
      el: blankEl
    })