Uri Gilad antishok

Promises reading list

This is a list of examples and articles, in roughly the order you should follow them, to show and explain how promises work and why you should use them. I'll probably add more things to this list over time.

This list primarily focuses on Bluebird, but the basic functionality should also work in ES6 Promises, and some examples are included on how to replicate Bluebird functionality with ES6 promises. You should still use Bluebird where possible, though - they are faster, less error-prone, and have more utilities.

I'm available for tutoring and code review :)

You may reuse all gists for any purpose under the WTFPL / CC0 (whichever you prefer).

"How do I get started with Node?" is a commonly heard question in #Node.js. This gist is an attempt to compile some of the answers to that question. It's a perpetual work-in-progress.

And if this list didn't quite answer your questions, I'm available for tutoring and code review! A donation is also welcome :)

Setting expectations

Before you get started learning about JavaScript and Node.js, there's one very important article you need to read: Teach Yourself Programming in Ten Years.

Understand that it's going to take time to learn Node.js, just like it would take time to learn any other specialized topic - and that you're not going to learn effectively just by reading things, or following tutorials or courses. _Get out there and build things!

The issue:

..mobile browsers will wait approximately 300ms from the time that you tap the button to fire the click event. The reason for this is that the browser is waiting to see if you are actually performing a double tap.

(from a new defunct https://developers.google.com/mobile/articles/fast_buttons article)

touch-action CSS property can be used to disable this behaviour.

touch-action: manipulation The user agent may consider touches that begin on the element only for the purposes of scrolling and continuous zooming. Any additional behaviors supported by auto are out of scope for this specification.

Read this first!

Hi there! Since this post was originally written, nvm has gained some new tools, and some people have suggested alternative (and potentially better) approaches for modern systems. Make sure to have a look at the comments to this article, before following this guide!

The original article

Trickier than it seems.

	;;
	;; NS CHEATSHEET
	;;
	;; * :require makes functions available with a namespace prefix
	;; and optionally can refer functions to the current ns.
	;;
	;; * :import refers Java classes to the current namespace.
	;;
	;; * :refer-clojure affects availability of built-in (clojure.core)
	;; functions.

	GitHub.TreeSlider = function () {
	if (!Modernizr.history) return;
	if ($("#slider").length == 0) return;
	if (navigator.userAgent.match(/(iPod\|iPhone\|iPad)/)) return;
	var a = this;
	a.enabled = !0, $("#slider a.js-slide-to, .breadcrumb a").live("click", function (b) {
	return a.clickHandler(b)
	}), $(window).bind("popstate", function (b) {
	a.popStateHandler(b.originalEvent)
	})

	[
	a: 1
	, b: 2
	, c: 3
	]

	[ a: 1
	, b: 2
	, c: 3
	]

	function attributes(xs, name) {
	return is_element(xs)? xs.getAttribute(name)
	: is_array(xs)? xs.map(attributes)
	: is_sequence(xs)? map(xs, attributes)
	: /* otherwise */ raise(TypeError('Not supported.'))
	}

	// vs

	function attributes(xs, name) {

	function copyFbRecord(oldRef, newRef) {
	oldRef.once('value', function(snap) {
	newRef.set( snap.value(), function(error) {
	if( error && typeof(console) !== 'undefined' && console.error ) { console.error(error); }
	});
	});
	}

	//taphover - a solution to the lack of hover on touch devices.
	//more info: http://www.hnldesign.nl/work/code/mouseover-hover-on-touch-devices-using-jquery/
	$('a.taphover').on('touchstart', function (e) {
	'use strict'; //satisfy the code inspectors
	var link = $(this); //preselect the link
	if (link.hasClass('hover')) {
	//preventDefault and return false will cause any other touches on the element(s) to fail.
	//to avoid this behavior data() will store the "href". so "href" can be restored.
	link.attr("href", link.data("href"));
	} else {