Marek Niepiekło niepiekm

My thoughts on MessagePack

Hi. My name is Sadayuki "Sada" Furuhashi. I am the author of the MessagePack serialization format as well as its implementation in C/C++/Ruby.

Recently, MessagePack made it to the front page of Hacker News with this blog entry by Olaf, the creator of the Facebook game ZeroPilot. In the comment thread, there were several criticisms for the blog post as well as MessagePack itself, and I thought this was a good opportunity for me to address the questions and share my thoughts.

My high-level response to the comments

To the best of my understanding, roughly speaking, the criticisms fell into the following two categories.

Locate the section for your github remote in the .git/config file. It looks like this:

[remote "origin"]
	fetch = +refs/heads/*:refs/remotes/origin/*
	url = [email protected]:joyent/node.git

Now add the line fetch = +refs/pull/*/head:refs/remotes/origin/pr/* to this section. Obviously, change the github url to match your project's URL. It ends up looking like this:

Branching

Quick Legend

Description, Instructions, Notes

Instance	Branch

Update (2019-05-06): The Broadcom wireless card in the MacBook Pro works and can be crammed into the Air.

Update (2015-12-04): This document used to be very lengthy as there were many manual steps required to get OpenBSD and Mac OS X working together through Boot Camp Assistant (BCA), which created a hybrid MBR and enabled a legacy BIOS emulation mode which older versions of Windows (and OpenBSD) required. Newer Macbooks stopped supporting older versions of Windows through BCA and now only support Windows 10 since it uses GPT and UEFI. However, now that newer versions of OpenBSD support GPT and UEFI, Boot Camp Assistant is no longer needed at all to boot OpenBSD.

macOS FileVault encryption and OpenBSD encrypted softraid on a Macbook Air/Pro

OpenBSD works pretty well on at least the Mid-2011 Macbook Air (A1370, SandyBridge) and Mid-2013 Macbook Air (Haswell). The new KMS code in 5.4 brings up the MBA's eDP display in 1366x768 with backlight

The Ultimate Git Alias Setup

If you use git on the command-line, you'll eventually find yourself wanting aliases for your most commonly-used commands. It's incredibly useful to be able to explore your repos with only a few keystrokes that eventually get hardcoded into muscle memory.

Some people don't add aliases because they don't want to have to adjust to not having them on a remote server. Personally, I find that having aliases doesn't mean I that forget the underlying commands, and aliases provide such a massive improvement to my workflow that it would be crazy not to have them.

The simplest way to add an alias for a specific git command is to use a standard bash alias.

# .bashrc

	?GetPort@HTTPServer@@QBEGXZ PROC ; HTTPServer::GetPort, COMDAT
	; _this$ = ecx
	mov ax, WORD PTR [ecx]
	ret 0

	exampleWithNumber: x

	"A method that illustrates every part of Smalltalk method syntax
	except primitives. It has unary, binary, and keyword messages,
	declares arguments and temporaries, accesses a global variable
	(but not and instance variable), uses literals (array, character,
	symbol, string, integer, float), uses the pseudo variables
	true false, nil, self, and super, and has sequence, assignment,
	return and cascade. It has both zero argument and one argument blocks."

	#! /usr/bin/env bash

	# Target and build configuration.
	TARGET=arm-none-eabi
	PREFIX=/opt/arm-none-eabi-4.7.1

	# Sources to build from.
	BINUTILS=binutils-2.23.1
	GCC=gcc-4.7.1
	NEWLIB=newlib-1.20.0

	#define _XOPEN_SOURCE 700
	#include <signal.h>
	#include <unistd.h>

	int main()
	{
	sigset_t set;
	int status;

	if (getpid() != 1) return 1;

	#ifndef FASTDELEGATE_H
	#define FASTDELEGATE_H

	#include <cstring>
	#include <type_traits>
	#include <cassert>
	#include <cstddef>
	#include <memory>
	#include <new>
	#include <utility>