Paul Smith paulsmith

Moved to https://jcs.org/notaweblog/2016/08/26/openbsd_chromebook/

These links no longer work. Springer have pulled the free plug.

Graduate texts in mathematics

duplicates = multiple editions

A Classical Introduction to Modern Number Theory, Kenneth Ireland Michael Rosen

The presentation in PDF format.
Publishing Landsat on AWS, the use of cloud infrastructure for public data distribution and processing.
On the size of Google Maps, now larger than most national mapping agencies.
OpenTripPlanner and OpenStreetMap, how open data and open source leverage each other and are in turn re-consumed by governmnet and civil society.
Michael H Goldhaber on the attention economy, a prescient take on content and the internet from 1997.
Google aquires Skybox Imaging.
Bibiana McHugh on Portland Trimet's [triple open strategy](https://prezi.com/vmydw-uwqalm/copy-of-you-complete

isoc

isoc is yet another "standard" container format.

It brings together the best bits of Docker Image Specification 1.0 and App Container Specification 0.3.0+git into a comprehensive yet portable container archive format, at the cost of a "few" duplicated bytes.

Layout

An isoc image is a appc image embedded in a docker image, but also a docker image embedded in a appc image. Some people might describe it as an iso-contained container format.

Rust is the first language that has emerged in the past few years that solves enough of my problems that it would be worth not only learning & teaching an entirely new language, but also sacrificing the maturity of the language ecosystems I’ve become accustomed to.

I highly suggest you read the "Guide" provided by the language developers or this won't make much sense. These are just some of my thoughts and are intended to highlight particular things that stand out to me. I am just a practitioner and not an expert in any of these languages, so I have probably made some incorrect assumptions and out-of-date assertions. Bare with me.

Rust feels like the first time momentum has gained behind a true systems programming language that uses modern PL design techniques to prevent common errors when dealing with memory. It seems like others have previously either been too anemic to be worth adopting or too abstract to provide proper control. The type system and assignment semantics are designed specifically to preven

Specification

Out Of The Tarpit

BOOM Analytics: Exploring Data-Centric, Declarative Programming for the Cloud

Dedalus: Datalog in Time and Space

Logic and Lattices for Distributed Programming

This is a type constructor

class FunctionType:
    def __init__(self, tyA, tyB):
        self.tyA = tyA
        self.tyB = tyB

    def __eq__(self, other):
 return self.tyA == other.tyA and self.tyB == other.tyB

	#!/bin/bash -e

	echo '
	PATH=$HOME/go/bin:$PATH
	export GOPATH=$HOME
	export CDPATH=.:$HOME/src/golang.org/x:$HOME/go/src:$HOME/src/github.com:$HOME/src/github.com/nf:$HOME/src/github.com/adg
	export EDITOR=vim
	' >> ~/.profile

	sudo apt-get update

	var Dialog = React.createClass({
	render: function() {
	// 1) render nothing, this way the DOM diff will never try to do
	// anything to it again, and we get a node to mess with
	return React.DOM.div();
	},

	componentDidMount: function() {
	// 2) do DOM lib stuff
	this.node = this.getDOMNode();