lattner

Swift Concurrency Manifesto

Author: Chris Lattner

Chinese Translation by Jason Yu

Contents

• Introduction
• Overall Vision

jamesyang124

Red Black Tree revisit.

	TIME
INSERTION	O(log n)
DELETION	O(log n)
SEARCH	O(log n)

| SPACE | O(n) |

seapy

RailsConf 2015 Schedule

RailsConf 2015 Room 202 Day 1

• Opening Keynote - DHH
• Prying Open The Black Box - Godfrey Chan
  • slide
• Riding Rails for 10 Years - John Duff
• DevOps for The Lazy - Aja Hammerly
• Docker isn’t just for deployment - Ben Dixon

drkarl

Linux Backup Solutions

I've been looking for the best Linux backup system, and also reading lots of HN comments.

Instead of putting pros and cons of every backup system I'll just list some deal-breakers which would disqualify them.

Also I would like that you, the HN community, would add more deal breakers for these or other backup systems if you know some more and at the same time, if you have data to disprove some of the deal-breakers listed here (benchmarks, info about something being true for older releases but is fixed on newer releases), please share it so that I can edit this list accordingly.

Amanda (comments by sammcj)

• It has a lot of management overhead and that's a problem if you don't have time for a full time backup administrator.

DmitrySoshnikov

/**
 * Educational Stack-based VM.
 *
 * See also:
 *  - More complex example with recursion: https://gist.github.com/DmitrySoshnikov/afda459222e96e6002ac
 *  - Register-based VM example: https://gist.github.com/DmitrySoshnikov/6407781
 *
 * by Dmitry Soshnikov <dmitry.soshnikov@gmail.com>
 * http://dmitrysoshnikov.com
 * MIT Stye License (C) 2015

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

sorbits

#!/usr/bin/env bash

progname=$(basename $0)
version="1.0 (2014-08-17)"
step=2

function create_hash {
	openssl dgst -sha1 -binary <<< "$1" | xxd -p
}

LeCoupa

/* *******************************************************************************************
 * THE UPDATED VERSION IS AVAILABLE AT
 * https://github.com/LeCoupa/awesome-cheatsheets
 * ******************************************************************************************* */


// 0. Synopsis.
// http://nodejs.org/api/synopsis.html

tsiege

ANNOUNCEMENT

I have moved this over to the Tech Interview Cheat Sheet Repo and has been expanded and even has code challenges you can run and practice against!






\

LeaVerou

(function(){
var log = console.log;

console.log = function(str) {
	var css = 'background: linear-gradient(to right, red, yellow, lime, aqua, blue, fuchsia, red); color: white; font-weight: bold;';
	var args = Array.prototype.slice.call(arguments);
	args[0] = '%c' + args[0];
	args.splice(1,0,css);
	return log.apply(console, args);
}