Brad Dougherty bdougherty

In Response to http://qfox.nl/weblog/282

Peter van der Zee published this post on his personal blog and it was featured in this week's edition of JavaScript Weekly. The following sections each contain a piece of code copied directly from his post, followed by an irrefutable explanation of why it is either wrong or misleading.

EDIT, April 1, 2013: I've removed any harsh language, but the content and corrections remain the same.

These are facts.

Computed properties...

Make it real

Ideas are cheap. Make a prototype, sketch a CLI session, draw a wireframe. Discuss around concrete examples, not hand-waving abstractions. Don't say you did something, provide a URL that proves it.

Ship it

Nothing is real until it's being used by a real user. This doesn't mean you make a prototype in the morning and blog about it in the evening. It means you find one person you believe your product will help and try to get them to use it.

	// In Chrome Canary, with Experimental JavaScript enabled...

	(function( exports ) {
	// Create a reusable symbol for storing
	// Emitter instance events

	var sym = new Symbol();

	function Emitter() {
	this[ sym ] = {

	// requestAnimationFrame implementation as a custom function to allow blacklisting
	// devices with broken implementation. Currently needs timer-based fallbacks for iOS 6.x for
	// code running inside <iframe> elements.
	// Uses polyfills based on http://paulirish.com/2011/requestanimationframe-for-smart-animating/
	(function() {

	var blacklisted = /iP(ad\|hone\|od).*OS 6/.test(window.navigator.userAgent),
	lastTime = 0,
	nativeRequest = window.requestAnimationFrame \|\| null,
	nativeCancel = window.cancelAnimationFrame \|\| null;

	// Taken from the commercial iOS PDF framework http://pspdfkit.com.
	// Copyright (c) 2014 Peter Steinberger, PSPDFKit GmbH. All rights reserved.
	// Licensed under MIT (http://opensource.org/licenses/MIT)
	//
	// You should only use this in debug builds. It doesn't use private API, but I wouldn't ship it.

	// PLEASE DUPE rdar://27192338 (https://openradar.appspot.com/27192338) if you would like to see this in UIKit.

	#import <objc/runtime.h>
	#import <objc/message.h>

	// Support routines for automatically reporting user timing for common analytics platforms
	// Currently supports Google Analytics, Boomerang and SOASTA mPulse
	// In the case of boomerang, you will need to map the event names you want reported
	// to timer names (for mPulse these need to be custom0, custom1, etc) using a global variable:
	// rumMapping = {'aft': 'custom0'};
	(function() {
	var wtt = function(n, t, b) {
	t = Math.round(t);
	if (t >= 0 && t < 3600000) {
	// Google Analytics

	After spending the better part of the month implementing date support
	in RethinkDB, Mike Lucy sent the team the following e-mail. It would
	have been funny, if it didn't cause thousands of programmers so much
	pain. Read it, laugh, and weep!

	-----

	So, it turns out that we're only going to support dates between the
	year 1400 and the year 10000 (inclusive), because that's what boost
	supports.

	<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
	<html>

	<head>
	<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
	<title>Single-Column Responsive Email Template</title>

	<style>
	@media only screen and (min-device-width: 541px) {
	.content {

	#!/usr/bin/env bash
	# MIT © Sindre Sorhus - sindresorhus.com

	# git hook to run a command after `git pull` if a specified file was changed
	# Run `chmod +x post-merge` to make it executable then put it into `.git/hooks/`.

	changed_files="$(git diff-tree -r --name-only --no-commit-id ORIG_HEAD HEAD)"

	check_run() {
	echo "$changed_files" \| grep --quiet "$1" && eval "$2"