montanaflynn

Foreground

• FgBlack = "\033[30m"
• FgRed = "\033[31m"
• FgGreen = "\033[32m"
• FgYellow = "\033[33m"
• FgBlue = "\033[34m"
• FgMagenta = "\033[35m"
• FgCyan = "\033[36m"
• FgWhite = "\033[37m"

kachayev

Channels Are Not Enough

... or Why Pipelining Is Not That Easy

Golang Concurrency Patterns for brave and smart.

By @kachayev

Intro

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.

---

TooTallNate

#!/usr/bin/env node

/**
 * A little script to play the ASCII Star Wars, but with a hidden cursor,
 * since over `telnet(1)` the cursor remains visible which is annoying.
 */

process.title = 'starwars'

var net = require('net')

ronaldsuwandi

function ls --description 'List contents of directory'
  command ls -lFG $argv
end

function subl --description 'Launches sublime text in a new window'
  command subl -n $argv
end

function code --description 'Launches visual code studio in a new window'
  command code -n $argv

ConradIrwin

# If you're looking into the C10M problem (10 million concurrent connections)
# you might want to play with DPDK (Originally proprietry Intel, now open source)
#
# C10M: http://c10m.robertgraham.com/
# DPDK: http://dpdk.org/
#
# This is a quick summary how to install dpdk on ubuntu
# running inside virtualbox on a mac

# On my Mac:

nijikokun

Road.js

Parallelization made easy in JavaScript / Node.js

Usage

var road = new Road();

road.onClear(function (error, results) { 

abeppu

var Twit = require("twit");
var config = require('./oauthconfig'); 

console.log("config:");
console.log(config);

var T = new Twit({
    consumer_key:  config.consumer_key,
    consumer_secret: config.consumer_secret,
    access_token: config.access_token,

jed

How to set up stress-free SSL on an OS X development machine

One of the best ways to reduce complexity (read: stress) in web development is to minimize the differences between your development and production environments. After being frustrated by attempts to unify the approach to SSL on my local machine and in production, I searched for a workflow that would make the protocol invisible to me between all environments.

Most workflows make the following compromises:

• Use HTTPS in production but HTTP locally. This is annoying because it makes the environments inconsistent, and the protocol choices leak up into the stack. For example, your web application needs to understand the underlying protocol when using the secure flag for cookies. If you don't get this right, your HTTP development server won't be able to read the cookies it writes, or worse, your HTTPS production server could pass sensitive cookies over an insecure connection.

• Use production SSL certificates locally. This is annoying

tylerneylon

-- Two dashes start a one-line comment.

--[[
     Adding two ['s and ]'s makes it a
     multi-line comment.
--]]

----------------------------------------------------
-- 1. Variables and flow control.
----------------------------------------------------