Antoine Bluchet soyuka

Spurred by recent events (https://news.ycombinator.com/item?id=8244700), this is a quick set of jotted-down thoughts about the state of "Semantic" Versioning, and why we should be fighting the good fight against it.

For a long time in the history of software, version numbers indicated the relative progress and change in a given piece of software. A major release (1.x.x) was major, a minor release (x.1.x) was minor, and a patch release was just a small patch. You could evaluate a given piece of software by name + version, and get a feeling for how far away version 2.0.1 was from version 2.8.0.

But Semantic Versioning (henceforth, SemVer), as specified at http://semver.org/, changes this to prioritize a mechanistic understanding of a codebase over a human one. Any "breaking" change to the software must be accompanied with a new major version number. It's alright for robots, but bad for us.

SemVer tries to compress a huge amount of information — the nature of the change, the percentage of users that wil

The introduction to Reactive Programming you've been missing

(by @andrestaltz)

This tutorial as a series of videos

If you prefer to watch video tutorials with live-coding, then check out this series I recorded with the same contents as in this article: Egghead.io - Introduction to Reactive Programming.

Python script to convert DBF database file to CSV

First download dbfpy: http://sourceforge.net/projects/dbfpy/files/latest/download?source=files
Then install: sudo python setup.py install

To convert DBF file to CSV:

./dbf2csv database.dbf

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.

Possible solutions

Connmanctl Cheat Sheet

Documentation @ http://git.kernel.org/cgit/network/connman/connman.git/tree/doc

Configure WiFi

Scan for access points (run multiple times for more complete scan):
```
  # connmanctl scan wifi
```

Scan completed for wifi

HLS streaming from node

Provided that you already have a file or stream segmenter generating your .m3u8 playlist and .ts segment files (such as the ffmpeg 'hls' muxer), this little node server will serve up those files to an HLS compatible client (e.g. Safari). If you're using node for your streaming app already, this obviates the need to serve the HLS stream from a separate web server.

loosely based on https://gist.github.com/bnerd/2011232

// loosely based on https://gist.github.com/bnerd/2011232
// requires node.js >= v0.10.0
// assumes that HLS segmenter filename base is 'out'
// and that the HLS playlist and .ts files are in the current directory

	var fs = require('fs');

	// Returns a buffer of the exact size of the input.
	// When endByte is read, stop reading from stdin.
	function getStdin(endByte) {
	var BUFSIZE = 256;
	var buf = new Buffer(BUFSIZE);
	var totalBuf = new Buffer(BUFSIZE);
	var totalBytesRead = 0;
	var bytesRead = 0;

	#!/usr/bin/env bash

	#
	# This is sp, the command-line Spotify controller. It talks to a running
	# instance of the Spotify Linux client over dbus, providing an interface not
	# unlike mpc.
	#
	# Put differently, it allows you to control Spotify without leaving the comfort
	# of your command line, and without a custom client or Premium subscription.
	#


	/*!
	* Bin-Packing by jakesgordon
	* https://github.com/jakesgordon/bin-packing/
	* Demo : http://codeincomplete.com/posts/2011/5/7/bin_packing/example/
	* Licence : https://github.com/jakesgordon/bin-packing/blob/master/LICENSE
	*/
	Packer = function(w, h) {
	this.init(w, h);
	};

	/**
	* Usage
	*
	$('.gradient').gradientGenerator({colors : ['green', 'yellow', 'red']});

	$('.change-color').on('click', function(e) {

	e.preventDefault();
	$('.gradient').gradientGenerator({
	colors : ['red', 'yellow', 'black'],