Maximilian Haack coffeejunk

Step 0:

Get Homebrew installed on your mac if you don't already have it

Step 1:

Install highlight. "brew install highlight". (This brings down Lua and Boost as well)

Step 2:

ruby-1.9.3-p327 cumulative performance patch for rbenv

This installs a patched ruby 1.9.3-p327 with various performance improvements and a backported COW-friendly GC, all courtesy of funny-falcon.

Requirements

You will also need a C Compiler. If you're on Linux, you probably already have one or know how to install one. On OS X, you should install XCode, and brew install autoconf using homebrew.

##How Homakov hacked GitHub and the line of code that could have prevented it

Please note: THIS ARTICLE IS NOT WRITTEN BY THE GITHUB TEAM or in any way associated with them. It's simply hosted as a Gist because the markdown formatting is excellent and far clearer than anything I could manage on my personal Tumblr at peternixey.com.

If you'd like to follow me on twitter my handle is @peternixey

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

Inheritance is a key concept in most object-oriented languages, but applying it skillfully can be challenging in practice. Back in 1989, M. Sakkinen wrote a paper called Disciplined inheritance that addresses these problems and offers some useful criteria for working around them. Despite being more than two decades old, this paper is extremely relevant to the modern Ruby programmer.

Sakkinen's central point seems to be that most traditional uses of inheritance lead to poor encapsulation, bloated object contracts, and accidental namespace collisions. He provides two patterns for disciplined inheritance and suggests that by normalizing the way that we model things, we can apply these two patterns to a very wide range of scenarios. He goes on to show that code that conforms to these design rules can easily be modeled as ordinary object composition, exposing a solid alternative to tradi


	// https://github.com/xetorthio/jedis
	import redis.clients.jedis.Jedis;

	import java.util.ArrayList;
	import java.util.List;
	import java.util.concurrent.ExecutionException;
	import java.util.concurrent.ExecutorService;
	import java.util.concurrent.Executors;
	import java.util.concurrent.Future;

	class ActionDispatch::Routing::Mapper
	def draw(routes_name)
	instance_eval(File.read(Rails.root.join("config/routes/#{routes_name}.rb")))
	end
	end

	BCX::Application.routes.draw do
	draw :api
	draw :account
	draw :session

	# Don't use this.
	import zmq
	import os

	class Worker:
	def __init__(self):
	print "parent: %d, pid: %d" % (os.getppid(), os.getpid())
	self.pid = os.getppid()
	self.context = zmq.Context()
	self.sub = self.context.socket(zmq.SUB)

	require 'active_model'

	# Most of this is the basic boilerplate described in the docs for active_model/errors; ie, the bare minimum
	# a class must have to use AM::Errors

	class Post
	extend ActiveModel::Naming

	attr_reader :errors
	attr_accessor :title, :author, :publication_date

	# A queue that you can pass to IO.select.
	#
	# NOT THREAD SAFE: Only one thread should write; only one thread should read.
	#
	# Purpose:
	# Allow easy integration of data-producing threads into event loops. The
	# queue will be readable from select's perspective as long as there are
	# objects in the queue.
	#
	# Implementation: