Sindre Sorhus sindresorhus

Measuring sync vs async child processes in Node.js

macOS 10.12.3
Node.js 7.4.0

childProcess

const childProcess = require('child_process');

Colours in terminal

It's a common confusion about terminal colours... Actually we have this:

plain ascii
ansi escape codes (16 colour codes with bold/italic and background)
256 colour palette (216 colours + 16 ansi + 24 gray) (colors are 24bit)
24bit true colour ("888" colours (aka 16 milion))

printf "\x1b[${bg};2;${red};${green};${blue}m\n"

Gettings started writing a ESLint rule

First, take a look at the ESLint rule documentation. Just skim it for now. It's very long and boring. You can come back to it later.

ESLint rules works on the AST (Abstract Syntax Tree) representation of the code. In short, this is a tree structure that describes the code in a very verbose form. ESLint walks this tree and rules can subscribe to be notified when it hits a specific node type, like a Literal type, which could be the "hello" part of const welcome = "hello";.

Go ahead and play around with some code in AST Explorer (Make sure the parser is espree). It's a great tool!

Here are some good articles on the subject (ignore the scaffolding parts):

https://insideops.wordpress.com/2015/12/08/creating-custom-rules-for-eslint/

	class SelectorWrapper<T> {
	let selector: Selector
	let closure: (T) -> Void

	init(withClosure closure: @escaping (T) -> Void) {
	self.selector = #selector(callClosure)
	self.closure = closure
	}

	@objc

	enum AssociationPolicy {
	case assign
	case retainNonatomic
	case copyNonatomic
	case retain
	case copy

	var rawValue: objc_AssociationPolicy {
	switch self {
	case .assign:

	final class AssociatedObject<T: Any> {
	subscript(index: Any) -> T? {
	get {
	return objc_getAssociatedObject(index, Unmanaged.passUnretained(self).toOpaque()) as! T?
	} set {
	objc_setAssociatedObject(index, Unmanaged.passUnretained(self).toOpaque(), newValue, .OBJC_ASSOCIATION_RETAIN_NONATOMIC)
	}
	}
	}

	APP_NAME = 'My App'
	TEAM_ID = 'XXXXXXXXXX'

	desc 'Create a beta build'
	task :build do
	# Start with a clean state
	build_dir = 'build'
	system %(rm -rf #{build_dir})

	# Build

	NSVisualEffectMaterial constants, and the undocumented materials they coorespond to in various modes:
	+----------------------+-------+----------+------+---------+
	\| MATERIAL # \| LIGHT \| LIGHT EM \| DARK \| DARK EM \|
	+----------------------+-------+----------+------+---------+
	\| \| \| \| \| \|
	\| 0 - Appearance Based \| 3 \| 3 \| 5 \| 5 \|
	\| \| \| \| \| \|
	\| 1 - Light \| 3 \| 3 \| 3 \| 3 \|
	\| \| \| \| \| \|
	\| 2 - Dark \| 4 \| 4 \| 4 \| 4 \|

	# In order for gpg to find gpg-agent, gpg-agent must be running, and there must be an env
	# variable pointing GPG to the gpg-agent socket. This little script, which must be sourced
	# in your shell's init script (ie, .bash_profile, .zshrc, whatever), will either start
	# gpg-agent or set up the GPG_AGENT_INFO variable if it's already running.

	# Add the following to your shell init to set up gpg-agent automatically for every shell
	if [ -f ~/.gnupg/.gpg-agent-info ] && [ -n "$(pgrep gpg-agent)" ]; then
	source ~/.gnupg/.gpg-agent-info
	export GPG_AGENT_INFO
	else