cryptix

package main

import (
	"archive/zip"
	"fmt"
	"log"
	"os"
	"time"

	"github.com/cryptix/go/logging"

icholy

// Use Case:
//
// Say you have a bunch of decoupled components which access the same set of databases.
// Since database/sql does connection pooling it makes sense for the components to share instances of *sql.DB
// This package lets you do that with minimal code changes.
package dbmanager

import (
	"database/sql"
	"time"

rjeczalik

#!/bin/bash

# Rafal Jeczalik <rjeczalik@gmail.com>
# https://gist.github.com/rjeczalik/db886c79049d83f318e2

type curl 1>/dev/null || exit
type jq 1>/dev/null || exit

die_usage() {
	if [ ! -z "${*}" ]; then

zankich

1. Install gort

• Download the appropriate binary for your system and architecture http://gort.io/documentation/getting_started/downloads/
• Extract the zip file and navigate to the directory with a terminal

2. Install arduino dependencies and flash firmata

• Make sure you are running your terminal as an Administrator
• $ ./gort arduino install
• reload your env variables, or close your cmd prompt and open a new one
• $ ./gort scan serial
• Take note of the COM port listed, this should be your arduino

stuart-warren

package main

import (
    "bytes"
    "code.google.com/p/go.crypto/openpgp"
    "encoding/base64"
    "io/ioutil"
    "log"
    "os"
)

kachayev

Channels Are Not Enough

... or Why Pipelining Is Not That Easy

Golang Concurrency Patterns for brave and smart.

By @kachayev

Intro

jashkenas

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

cryptix

package main

import (
	"math/rand"
	"net"

	"github.com/cryptix/goremutake"
	"github.com/ftrvxmtrx/fd"
)

momer

package main

import (
    "myapp/webserver/app/common"
    "github.com/golang/glog"
    "github.com/gorilla/mux"
    "encoding/json"
    "strconv"
    "flag"
    "fmt"

staltz

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.

---