Brandon Moore brandonkm

This is unmaintained, please visit Ben-PH/spacemacs-cheatsheet

Useful Spacemacs commands

SPC q q - quit
SPC w / - split window vertically
SPC w - - split window horizontally
SPC 1 - switch to window 1
SPC 2 - switch to window 2
SPC w c - delete current window

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

BBQ.js

Ruth Baril—Barriers To Entry: Learning to Program is the Easy Part

Browserified

Stephen Belanger—Browserifying Big Projects With Minimal Rage
Nicolas Bevacqua—Browserify All The Things
James Halliday—Brick The Web

Original link: http://www.concentric.net/~Ttwang/tech/inthash.htm
Taken from: http://web.archive.org/web/20071223173210/http://www.concentric.net/~Ttwang/tech/inthash.htm
Reformatted using pandoc

Integer Hash Function

Thomas Wang, Jan 1997

last update Mar 2007

I'm having trouble understanding the benefit of require.js. Can you help me out? I imagine other developers have a similar interest.

From Require.js - Why AMD:

The AMD format comes from wanting a module format that was better than today's "write a bunch of script tags with implicit dependencies that you have to manually order"

I don't quite understand why this methodology is so bad. The difficult part is that you have to manually order dependencies. But the benefit is that you don't have an additional layer of abstraction.

If like me you find it frustrating to define the same vendor prefixes over and over again. Sure, you might create mixins that help reduce the amount of repetitiveness but when your mixins file becomes a library (or not) you see so many lines of near-identical code and wonder if there is an easier way.

Say you have this (all-too familiar) mixin:

@mixin border-radius($radius) {
  -webkit-border-radius: $radius;
  -moz-border-radius: $radius;
  -ms-border-radius: $radius;
 -o-border-radius: $radius;

	[My initial list:]

	DRM
	speed for superhi-perf games
	app store placement
	source-code secrecy

	[list compiled from other people's twitter answers; thanks all!]

	pushing native notifications when they're not in the "app" (several people said this)

	/**********************************************/
	/*
	/*
	/* Crate -- Theme for Chrome DevTools
	/* Last Update :: September 2013
	/*
	/* based on:
	/* mnml by Michael P. Pfeiffer
	/* Based on a Gist by Ben Truyman. Further attr:
	/* https://gist.github.com/3040634

	/*
	To use it:

	require(['video'], function(Video){
	var video = new Video('.video');
	// optionally, you can either drag a video file over the .video element
	video.playvideo('a valid video url');
	});

	*/