Ján Dzurek famousgarkin

Reader Macros in Common Lisp

This post also appears on lisper.in.

Reader macros are perhaps not as famous as ordinary macros. While macros are a great way to create your own DSL, reader macros provide even greater flexibility by allowing you to create entirely new syntax on top of Lisp.

Paul Graham explains them very well in [On Lisp][] (Chapter 17, Read-Macros):

The three big moments in a Lisp expression's life are read-time, compile-time, and runtime. Functions are in control at runtime. Macros give us a chance to perform transformations on programs at compile-time. ...read-macros... do their work at read-time.

Description

PLEASE SCROLL DOWN AND READ THE COMMENTS FOR A MORE UP TO DATE WAY (AND EASIER) TO DO THIS
When using Homebrew (http://brew.sh) and searching formulas or pull requests you may get the dreaded error message: Github API Rate limit exceeded

Let's fix that! (yeah!)

Short version

PLEASE SCROLL DOWN AND READ THE COMMENTS FOR A MORE UP TO DATE WAY (AND EASIER) TO DO THIS

Moved to git-repository: https://github.com/denji/awesome-http-benchmark

Tools

Located in alphabetical order (not prefer)

ab – slow and single threaded, written in C
apib – most of the features of ApacheBench (ab), also designed as a more modern replacement, written in C
autocannon – fast HTTP/1.1 benchmarking tool written in Node.js
baloo – Expressive end-to-end HTTP API testing made easy, written in Go (golang)

Better local require() paths for Node.js

Problem

When the directory structure of your Node.js application (not library!) has some depth, you end up with a lot of annoying relative paths in your require calls like:

const Article = require('../../../../app/models/article');

Those suck for maintenance and they're ugly.

	#! /bin/sh

	### Must have Gcloud sdk installed and configured

	###Create a micro instance as ansible master
	gcloud compute --project $PROJECT_NAME instances create "ansible" --zone "us-central1-b" --machine-type "f1-micro" --network "default" --maintenance-policy "MIGRATE" --scopes "https://www.googleapis.com/auth/userinfo.email" "https://www.googleapis.com/auth/compute" "https://www.googleapis.com/auth/devstorage.full_control" --tags "http-server" "https-server" --no-boot-disk-auto-delete

	###or a centos like in the tutorial
	gcloud compute --project $PROJECT_NAME instances create "ansible-master" --zone "us-central1-b" --machine-type "g1-small" --network "default" --maintenance-policy "MIGRATE" --scopes "https://www.googleapis.com/auth/userinfo.email" "https://www.googleapis.com/auth/compute" "https://www.googleapis.com/auth/devstorage.full_control" --tags "http-server" "https-server" --image "https://www.googleapis.com/compute/v1/projects/centos-cloud/global/images/centos-7-v20140926" --no-boot-disk-auto-de

	# Template composition with inclusion
	Every template language I have seen provides some mechanism for one template to include another, thus supporting the reuse of repeated elements like headers and footers. The included templates are called partials in Mustache parlance:

	```html
	<!-- home.hbs -->
	<html>
	<body>
	{{> header}}
	<p> HOME </p>
	{{> footer}}

	- name: Testing variables with SUDO=NO
	hosts: "*"
	sudo: no

	tasks:
	- name: "PLAYBOOK SUDO=NO, TASK SUDO=NO"
	command: whoami
	register: whoami_output
	sudo: no
	- debug: var=whoami_output.stdout

	# A VirtualBox bug forces vagrant to serve
	# corrupt files via Apache or nginx
	# The solution to that would be to turn off
	# the SendFile option in apache or nginx
	#
	# If you use apache as your main web server
	# add this directive in your httpd.conf (or apache.conf)
	# configuration file name may vary in various systems
	#
	EnableSendfile off

	# Assuming an Ubuntu Docker image
	$ docker run -it <image> /bin/bash