jessfraz

server {
	....
  
	location ~ ^/x/(.*) {
		if ($args = "go-get=1") {
			add_header Content-Type text/html;
			return 200 '<meta name="go-import" content="$host/x/$1 git https://github.com/jessfraz/$1.git">';
		}
		return 302 https://github.com/jessfraz/$1;
	}

paulirish

What forces layout / reflow

All of the below properties or methods, when requested/called in JavaScript, will trigger the browser to synchronously calculate the style and layout*. This is also called reflow or layout thrashing, and is common performance bottleneck.

Generally, all APIs that synchronously provide layout metrics will trigger forced reflow / layout. Read on for additional cases and details.

Element APIs

Getting box metrics

• elem.offsetLeft, elem.offsetTop, elem.offsetWidth, elem.offsetHeight, elem.offsetParent

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.

---

macintux

This is not intended to be comprehensive or authoritative, just free online resources I've found valuable while learning more about Erlang.

Similar lists

• 0xAX's list of Erlang bookmarks
• Federico Carrone, Erlang Spawned Shelter
• Ivan Uemlianin's list of resources on various BEAM languages
• David Robakowski's curated list of awesome Erlang libraries, resources and shiny things
• Julius Beckmann's curated list of amazingly awesome Elixir and Erlang libraries, resources and shiny things

Instruction

passy

Yeoman + Compass Sprites

Setup

generator-webapp has support for compass out of the box. However, in order to use one of my favorite features of it — sprites and the image_url helper — you have to make some adjustments to the Gruntfile.

Let's assume you use a SASS stylesheet like this one:

@import "design/*.png"

ordinaryzelig

I'm a fan of MiniTest::Spec. It strikes a nice balance between the simplicity of TestUnit and the readable syntax of RSpec. When I first switched from RSpec to MiniTest::Spec, one thing I was worried I would miss was the ability to add matchers. (A note in terminology: "matchers" in MiniTest::Spec refer to something completely different than "matchers" in RSpec. I won't get into it, but from now on, let's use the proper term: "expectations").

Understanding MiniTest::Expectations

Let's take a look in the code (I'm specifically referring to the gem, not the standard library that's built into Ruby 1.9):

# minitest/spec.rb

module MiniTest::Expectations