Tour of language landscape (code.talks)

233
tour guide : Yan Cui @theburningmonk

Transcript of Tour of language landscape (code.talks)

Page 1: Tour of language landscape (code.talks)

tour guide : Yan Cui @theburningmonk

Page 2: Tour of language landscape (code.talks)

Hi, my name is Yan Cui.

Page 3: Tour of language landscape (code.talks)
Page 4: Tour of language landscape (code.talks)

agenda

Page 5: Tour of language landscape (code.talks)

Type Provider Pipes

Statically Resolved TP Implicit Interface Implementation

Borrowed Pointers Dependent Types

Uniqueness Types

Bit SyntaxSignals

Macros

Unit-of-Measure

Actor Model

Page 6: Tour of language landscape (code.talks)

disclaimers

Page 7: Tour of language landscape (code.talks)

“Programming languages have a devious influence: they shape our thinking

habits.”

- Edsger W. Dijkstra

Page 8: Tour of language landscape (code.talks)

“One of the most disastrous thing we can learn is the first programming language, even

if it's a good programming language.”

- Alan Kay

Page 9: Tour of language landscape (code.talks)

“The limits of my language means the limits

of my world.”

- Ludwig Wittgenstein

Page 10: Tour of language landscape (code.talks)

“We cannot solve our problems with the same thinking we used when

we created them.”

- Albert Einstein

Page 11: Tour of language landscape (code.talks)

Type Provider Pipes

Statically Resolved TP Implicit Interface Implementation

Borrowed Pointers Dependent Types

Uniqueness Types

Bit SyntaxSignals

Macros

Unit-of-Measure

Actor Model

Page 12: Tour of language landscape (code.talks)
Page 13: Tour of language landscape (code.talks)

your app

Page 14: Tour of language landscape (code.talks)

your app

CSVCSVCSV

CSVCSVXML

Page 15: Tour of language landscape (code.talks)

your app

CSVCSVCSV

CSVCSVXML

some service

Page 16: Tour of language landscape (code.talks)

your app

CSVCSVCSV

CSVCSVXML

some service

DB

Page 17: Tour of language landscape (code.talks)

1. define DTO types2. I/O3. marshal data into DTO4. do useful work

Page 18: Tour of language landscape (code.talks)

1. define DTO types2. I/O3. marshal data into DTO4. do useful work

Page 19: Tour of language landscape (code.talks)

compilerprovideexternal

data source typed info

Page 20: Tour of language landscape (code.talks)

type providers

Page 21: Tour of language landscape (code.talks)

intellisensetooltips

Page 22: Tour of language landscape (code.talks)
Page 23: Tour of language landscape (code.talks)
Page 24: Tour of language landscape (code.talks)

compile time validation

Page 25: Tour of language landscape (code.talks)

no code generation

Page 26: Tour of language landscape (code.talks)

R

FunScript AzureAmazon S3

CSVSQLiteSQL Server

WSDL

WorldBank

RegexODATA IKVM

FacebookApiary

XAMLFreebaseHadoop

Oracle

Minesweeper

Don SymePowershell

JSON

Fizzbuzz

Mixin

RSS

MatlabDates

NorthPole

XML

Python

Page 27: Tour of language landscape (code.talks)

Type Provider Pipes

Statically Resolved TP Implicit Interface Implementation

Borrowed Pointers Dependent Types

Uniqueness Types

Bit SyntaxSignals

Macros

Unit-of-Measure

Actor Model

Page 28: Tour of language landscape (code.talks)

“…a clean design is one that supports visual thinking so

people can meet their informational needs with a

minimum of conscious effort.”

- Daniel Higginbotham (www.visualmess.com)

Page 29: Tour of language landscape (code.talks)

Whilst talking with an ex-colleague, a question came up on how to implement the Stable Marriage problem using a message passing approach. Naturally, I wanted to answer that question with Erlang!

Let’s first dissect the problem and decide what processes we need and how they need to interact with one another.

The stable marriage problem is commonly stated as:Given n men and n women, where each person has ranked all members of the opposite sex with a unique number between 1 and n in order of preference, marry the men and women together such that there are no two people of opposite sex who would both rather have each other than their current partners. If there are no such people, all the marriages are “stable”. (It is assumed that the participants are binary gendered and that marriages are not same-sex).From the problem description, we can see that we need:* a module for man* a module for woman* a module for orchestrating the experimentIn terms of interaction between the different modules, I imagined something along the lines of…

how we read ENGLISH

see also http://bit.ly/1KN8cd0

Page 30: Tour of language landscape (code.talks)

Whilst talking with an ex-colleague, a question came up on how to implement the Stable Marriage problem using a message passing approach. Naturally, I wanted to answer that question with Erlang!

Let’s first dissect the problem and decide what processes we need and how they need to interact with one another.

The stable marriage problem is commonly stated as:Given n men and n women, where each person has ranked all members of the opposite sex with a unique number between 1 and n in order of preference, marry the men and women together such that there are no two people of opposite sex who would both rather have each other than their current partners. If there are no such people, all the marriages are “stable”. (It is assumed that the participants are binary gendered and that marriages are not same-sex).From the problem description, we can see that we need:* a module for man* a module for woman* a module for orchestrating the experimentIn terms of interaction between the different modules, I imagined something along the lines of…

2. top-to-bottom1.left-to-right

how we read ENGLISH

see also http://bit.ly/1KN8cd0

Page 31: Tour of language landscape (code.talks)

how we read CODE

public void DoSomething(int x, int y){ Foo(y, Bar(x, Zoo(Monkey())));}

see also http://bit.ly/1KN8cd0

Page 32: Tour of language landscape (code.talks)

how we read CODE

public void DoSomething(int x, int y){ Foo(y, Bar(x, Zoo(Monkey())));}

2. bottom-to-top

1.right-to-left

see also http://bit.ly/1KN8cd0

Page 33: Tour of language landscape (code.talks)

Whilst talking with an ex-colleague, a question came up on how to implement the Stable Marriage problem using a message passing approach. Naturally, I wanted to answer that question with Erlang!

Let’s first dissect the problem and decide what processes we need and how they need to interact with one another.

The stable marriage problem is commonly stated as:Given n men and n women, where each person has ranked all members of the opposite sex with a unique number between 1 and n in order of preference, marry the men and women together such that there are no two people of opposite sex who would both rather have each other than their current partners. If there are no such people, all the marriages are “stable”. (It is assumed that the participants are binary gendered and that marriages are not same-sex).From the problem description, we can see that we need:* a module for man* a module for woman* a module for orchestrating the experimentIn terms of interaction between the different modules, I imagined something along the lines of…

2. top-to-bottom

1.left-to-right

how we read ENGLISH

public void DoSomething(int x, int y){ Foo(y, Bar(x, Zoo(Monkey())));}

2. top-to-bottom

1.right-to-left

how we read CODE

see also http://bit.ly/1KN8cd0

Page 34: Tour of language landscape (code.talks)

“…a clean design is one that supports visual thinking so

people can meet their informational needs with a

minimum of conscious effort.”

Page 35: Tour of language landscape (code.talks)

|>

Page 36: Tour of language landscape (code.talks)

how we read CODE

let drawCircle x y radius = radius |> circle |> filled (rgb 150 170 150) |> alpha 0.5 |> move (x, y)

see also http://bit.ly/1KN8cd0

Page 37: Tour of language landscape (code.talks)

how we read CODE

let drawCircle x y radius = radius |> circle |> filled (rgb 150 170 150) |> alpha 0.5 |> move (x, y)

2. top-to-bottom1.left-to-right

see also http://bit.ly/1KN8cd0

Page 38: Tour of language landscape (code.talks)

let drawCircle x y radius = circle radius |> filled (rgb 150 170 150) |> alpha 0.5 |> move (x, y)

see also http://bit.ly/1KN8cd0

Page 39: Tour of language landscape (code.talks)

let drawCircle x y radius = circle radius |> filled (rgb 150 170 150) |> alpha 0.5 |> move (x, y)

see also http://bit.ly/1KN8cd0

Page 40: Tour of language landscape (code.talks)

let drawCircle x y radius = circle radius |> filled (rgb 150 170 150) |> alpha 0.5 |> move (x, y)

see also http://bit.ly/1KN8cd0

Page 41: Tour of language landscape (code.talks)

Type Provider Pipes

Statically Resolved TP Implicit Interface Implementation

Borrowed Pointers Dependent Types

Uniqueness Types

Bit SyntaxSignals

Macros

Unit-of-Measure

Actor Model

Page 42: Tour of language landscape (code.talks)

NASA orbiter crashed because one engineer accidentally used miles instead of kilometres

Page 43: Tour of language landscape (code.talks)

you’re never too smart to make mistakes

Page 44: Tour of language landscape (code.talks)

unit-of-measure

Page 45: Tour of language landscape (code.talks)

[<Measure>]type Pence

e.g. 42<Pence>153<Pence>…

Page 46: Tour of language landscape (code.talks)

10<Meter> / 2<Second> = 5<Meter/Second>10<Meter> * 2<Second> = 20<Meter Second> 10<Meter> + 10<Meter> = 20<Meter>10<Meter> * 10 = 100<Meter>10<Meter> * 10<Meter> = 100<Meter2>10<Meter> + 2<Second> // error10<Meter> + 2 // error

Page 47: Tour of language landscape (code.talks)

10<Meter> / 2<Second> = 5<Meter/Second>10<Meter> * 2<Second> = 20<Meter Second> 10<Meter> + 10<Meter> = 20<Meter>10<Meter> * 10 = 100<Meter>10<Meter> * 10<Meter> = 100<Meter2>10<Meter> + 2<Second> // error10<Meter> + 2 // error

Page 48: Tour of language landscape (code.talks)
Page 49: Tour of language landscape (code.talks)

Type Provider Pipes

Statically Resolved TP Implicit Interface Implementation

Borrowed Pointers Dependent Types

Uniqueness Types

Bit SyntaxSignals

Macros

Unit-of-Measure

Actor Model

Page 50: Tour of language landscape (code.talks)

Duck Typing

If it looks like a duck and quacks like a duck, it's a duck

Page 51: Tour of language landscape (code.talks)

def say_quack(duck): duck.quack()

Page 52: Tour of language landscape (code.talks)

def say_quack(duck): duck.quack()

Page 53: Tour of language landscape (code.talks)

class Duck: def quack(self): print("quack quack!”)

Page 54: Tour of language landscape (code.talks)

class Duck: def quack(self): print("quack quack!”)

duck = Duck() say_quack(duck)

> quack quack!

Page 55: Tour of language landscape (code.talks)

class Bird: def quack(self): print(“tweet tweet!”)

Page 56: Tour of language landscape (code.talks)

class Bird: def quack(self): print(“tweet tweet!”)

bird = Bird() say_quack(bird)

> tweet tweet!

Page 57: Tour of language landscape (code.talks)

ConvenienceSafety

Page 58: Tour of language landscape (code.talks)

what if…

Page 59: Tour of language landscape (code.talks)

Convenience Safety

see also http://bit.ly/1H2fN9i

Page 60: Tour of language landscape (code.talks)

implicit interface

implementation

Page 61: Tour of language landscape (code.talks)

type Duck interface { Quack() }

see also http://bit.ly/1ER5zVs

Page 62: Tour of language landscape (code.talks)

func sayQuack(duck Duck) { duck.Quack() }

see also http://bit.ly/1ER5zVs

Page 63: Tour of language landscape (code.talks)

type Donald struct { } func (d Donald) Quack() { fmt.Println(“quack quack!”) }

see also http://bit.ly/1ER5zVs

Page 64: Tour of language landscape (code.talks)

type Bird struct { } func (b Bird) Quack() { fmt.Println(“tweet tweet!”) }

see also http://bit.ly/1ER5zVs

Page 65: Tour of language landscape (code.talks)

func main() { donald := Donald{} sayQuack(donald) bird := Bird{} sayQuack(bird) }

see also http://bit.ly/1ER5zVs

Page 66: Tour of language landscape (code.talks)

quack quack!

func main() { donald := Donald{} sayQuack(donald) bird := Bird{} sayQuack(bird) }

Page 67: Tour of language landscape (code.talks)

tweet tweet!

func main() { donald := Donald{} sayQuack(donald) bird := Bird{} sayQuack(bird) }

Page 68: Tour of language landscape (code.talks)

type Dog struct { } func (d Dog) Bark() { fmt.Println(“woof woof!”) }

see also http://bit.ly/1ER5zVs

Page 69: Tour of language landscape (code.talks)

func main() { dog := Dog{} sayQuack(dog) }

main.go:40: cannot use dog (type Dog) as type Duck in argument to sayQuack:

Dog does not implement Duck (missing Quack method)

see also http://bit.ly/1ER5zVs

Page 70: Tour of language landscape (code.talks)

patterns are observed after the fact

see also http://bit.ly/1ER5zVs

Page 71: Tour of language landscape (code.talks)

system building is also a process of learning

and discovery

see also http://bit.ly/1ER5zVs

Page 72: Tour of language landscape (code.talks)

implementation package

interface packagesee also http://bit.ly/1ER5zVs

Page 73: Tour of language landscape (code.talks)

encourages precise interface definitions

see also http://bit.ly/1ER5zVs

Page 74: Tour of language landscape (code.talks)
Page 75: Tour of language landscape (code.talks)

Type Provider Pipes

Statically Resolved TP Implicit Interface Implementation

Borrowed Pointers Dependent Types

Uniqueness Types

Bit SyntaxSignals

Macros

Unit-of-Measure

Actor Model

Page 76: Tour of language landscape (code.talks)

Homoiconicity

…homoiconicity is a property of some programming languages in which the program structure is similar to its syntax, and therefore the program’s internal representation can be

inferred by reading the text’s layout…

Page 77: Tour of language landscape (code.talks)

code is data data is code

Page 78: Tour of language landscape (code.talks)

(let [x 1] (inc x))

see also http://bit.ly/1PpIrjS

Page 79: Tour of language landscape (code.talks)

(let [x 1] (inc x))

=> 2

see also http://bit.ly/1PpIrjS

Page 80: Tour of language landscape (code.talks)

list (1 2 3) vector [1 2 3]

see also http://bit.ly/1PpIrjS

Page 81: Tour of language landscape (code.talks)

(let [x 1] (inc x))

list

see also http://bit.ly/1PpIrjS

Page 82: Tour of language landscape (code.talks)

(let [x 1] (inc x))

symbol

see also http://bit.ly/1PpIrjS

Page 83: Tour of language landscape (code.talks)

(let [x 1] (inc x))

vector

see also http://bit.ly/1PpIrjS

Page 84: Tour of language landscape (code.talks)

(let [x 1] (inc x))

list

see also http://bit.ly/1PpIrjS

Page 85: Tour of language landscape (code.talks)

form : code as data structure

see also http://bit.ly/1PpIrjS

Page 86: Tour of language landscape (code.talks)

code data

quote

eval

see also http://bit.ly/1PpIrjS

Page 87: Tour of language landscape (code.talks)

quote

(+ 1 2) => 3

see also http://bit.ly/1PpIrjS

Page 88: Tour of language landscape (code.talks)

quote

(+ 1 2) => 3 (quote (+ 1 2)) => (+ 1 2)

see also http://bit.ly/1PpIrjS

Page 89: Tour of language landscape (code.talks)

quote

(+ 1 2) => 3 (quote (+ 1 2)) => (+ 1 2) ‘(+ 1 2) => (+ 1 2)see also http://bit.ly/1PpIrjS

Page 90: Tour of language landscape (code.talks)

eval

‘(+ 1 2) => (+ 1 2) (eval ‘(+ 1 2)) => 3

see also http://bit.ly/1PpIrjS

Page 91: Tour of language landscape (code.talks)

macros

Page 92: Tour of language landscape (code.talks)

(defmacro assert-equals [actual expected] ‘(let [actual-val# ~actual] (when-not (= actual-val# ~expected) (throw (AssertionError. (str “FAIL in “ ‘~actual “\n expected: “ ‘~expected “\n actual: “ actual-val#))))))

see also http://bit.ly/1PpIrjS

Page 93: Tour of language landscape (code.talks)

(assert-equals (inc 1) 2) ; => nil (assert-equals (inc 1) (+ 0 1)) ; => AssertionError FAIL in (inc 1) ; expected: (+ 0 1) ; actual: 2

see also http://bit.ly/1PpIrjS

Page 94: Tour of language landscape (code.talks)

(assert-equals (inc 1) 2) ; => nil (assert-equals (inc 1) (+ 0 1)) ; => AssertionError FAIL in (inc 1) ; expected: (+ 0 1) ; actual: 2

see also http://bit.ly/1PpIrjS

Page 95: Tour of language landscape (code.talks)

(assert-equals (inc 1) 2) ; => nil (assert-equals (inc 1) (+ 0 1)) ; => AssertionError FAIL in (inc 1) ; expected: (+ 0 1) ; actual: 2

see also http://bit.ly/1PpIrjS

huh?? where? what? how?

Page 96: Tour of language landscape (code.talks)

(defmacro assert-equals [actual expected] ‘(let [actual-val# ~actual] (when-not (= actual-val# ~expected) (throw (AssertionError. (str “FAIL in “ ‘~actual “\n expected: “ ‘~expected “\n actual: “ actual-val#))))))

(assert-equals (inc 1) (+ 0 1))

see also http://bit.ly/1PpIrjS

Page 97: Tour of language landscape (code.talks)

(defmacro assert-equals [actual expected] ‘(let [actual-val# ~actual] (when-not (= actual-val# ~expected) (throw (AssertionError. (str “FAIL in “ ‘~actual “\n expected: “ ‘~expected “\n actual: “ actual-val#))))))

(assert-equals (inc 1) (+ 0 1))

see also http://bit.ly/1PpIrjS

Page 98: Tour of language landscape (code.talks)

(defmacro assert-equals [actual expected] ‘(let [actual-val# ~actual] (when-not (= actual-val# ~expected) (throw (AssertionError. (str “FAIL in “ ‘~actual “\n expected: “ ‘~expected “\n actual: “ actual-val#))))))

(assert-equals (inc 1) (+ 0 1))

see also http://bit.ly/1PpIrjS

Page 99: Tour of language landscape (code.talks)

see also http://bit.ly/1PpIrjS

(defmacro assert-equals [actual expected] ‘(let [actual-val# ~actual] (when-not (= actual-val# ~expected) (throw (AssertionError. (str “FAIL in “ ‘~actual “\n expected: “ ‘~expected “\n actual: “ actual-val#))))))

Page 100: Tour of language landscape (code.talks)

see also http://bit.ly/1PpIrjS

(defmacro assert-equals [actual expected] ‘(let [actual-val# ~actual] (when-not (= actual-val# ~expected) (throw (AssertionError. (str “FAIL in “ ‘~actual “\n expected: “ ‘~expected “\n actual: “ actual-val#))))))

‘(

Page 101: Tour of language landscape (code.talks)

expanded at compile time

see also http://bit.ly/1PpIrjS

Page 102: Tour of language landscape (code.talks)

see also http://bit.ly/1PpIrjS

(macroexpand '(assert-equals (inc 1) (+ 0 1))) ; => ; (let* [actual-value__16087__auto__ (inc 1)] ; (clojure.core/when-not ; (clojure.core/= actual-value__16087__auto__ (+ 0 1)) ; (throw (java.lang.AssertionError. ; (clojure.core/str ; "FAIL in " (quote (inc 1)) ; "\nexpected: " (quote (+ 0 1)) ; "\n actual: " actual-value__16087__auto__)))))

Page 103: Tour of language landscape (code.talks)
Page 104: Tour of language landscape (code.talks)

Type Provider Pipes

Statically Resolved TP Implicit Interface Implementation

Borrowed Pointers Dependent Types

Uniqueness Types

Bit SyntaxSignals

Macros

Unit-of-Measure

Actor Model

Page 105: Tour of language landscape (code.talks)

GC is great

Page 106: Tour of language landscape (code.talks)

runtime cost

Page 107: Tour of language landscape (code.talks)

ownership

see also http://bit.ly/1F6WBVD

Page 108: Tour of language landscape (code.talks)

memory safety without GC

see also http://bit.ly/1F6WBVD

Page 109: Tour of language landscape (code.talks)

ZERO runtime cost

see also http://bit.ly/1F6WBVD

Page 110: Tour of language landscape (code.talks)

safety + speed

see also http://bit.ly/1F6WBVD

Page 111: Tour of language landscape (code.talks)

fn foo() { // v has ownership of the vector let v = vec![1, 2, 3]; // mutable binding let mut v2 = vec![]; } // vector is deallocated at the // end of scope, // this happens deterministically

see also http://bit.ly/1F6WBVD

Page 112: Tour of language landscape (code.talks)

immutable by default

see also http://bit.ly/1F6WBVD

Page 113: Tour of language landscape (code.talks)

// take ownership let v = vec![1, 2, 3];

see also http://bit.ly/1F6WBVD

Page 114: Tour of language landscape (code.talks)

// take ownership let v = vec![1, 2, 3];

// moved ownership to v2 let v2 = v;

see also http://bit.ly/1F6WBVD

Page 115: Tour of language landscape (code.talks)

// take ownership let v = vec![1, 2, 3];

// moved ownership to v2 let v2 = v;

println!("v[0] is {}", v[0]); // error: use of moved value: `v` // println!("v[0] is {}", v[0]); // ^

see also http://bit.ly/1F6WBVD

Page 116: Tour of language landscape (code.talks)

fn take(v : Vec<i32>) { // ownership of vector transferred // to v in this scope }

see also http://bit.ly/1F6WBVD

Page 117: Tour of language landscape (code.talks)

// take ownership let v = vec![1, 2, 3];

// moved ownership take(v);

see also http://bit.ly/1F6WBVD

Page 118: Tour of language landscape (code.talks)

// take ownership let v = vec![1, 2, 3];

// moved ownership take(v);

println!("v[0] is {}", v[0]); // error: use of moved value: `v` // println!("v[0] is {}", v[0]); // ^

see also http://bit.ly/1F6WBVD

Page 119: Tour of language landscape (code.talks)

see also http://bit.ly/1F6WBVD

Page 120: Tour of language landscape (code.talks)

see also http://bit.ly/1F6WBVD

let me buy your book

Page 121: Tour of language landscape (code.talks)

see also http://bit.ly/1F6WBVD

sure thing!

Page 122: Tour of language landscape (code.talks)

see also http://bit.ly/1F6WBVD

thanks

Page 123: Tour of language landscape (code.talks)

see also http://bit.ly/1F6WBVD

BURN!!! >:D

Page 124: Tour of language landscape (code.talks)

see also http://bit.ly/1F6WBVD

but I still need it..

:’(

Page 125: Tour of language landscape (code.talks)

borrowing

see also http://bit.ly/1F6WBVD

Page 126: Tour of language landscape (code.talks)

// note we're taking a reference, // &Vec<i32>, instead of Vec<i32> fn take(v : &Vec<i32>) { // no need to deallocate the vector // after we go out of scope here }

see also http://bit.ly/1F6WBVD

Page 127: Tour of language landscape (code.talks)

// take ownership let v = vec![1, 2, 3];

// notice we're passing a reference, // &v, instead of v take(&v); // borrow ownership

println!("v[0] is {}", v[0]); // v[0] is 1

see also http://bit.ly/1F6WBVD

Page 128: Tour of language landscape (code.talks)

see also http://bit.ly/1F6WBVD

let me borrow your

book

Page 129: Tour of language landscape (code.talks)

see also http://bit.ly/1F6WBVD

sure thing!

Page 130: Tour of language landscape (code.talks)

see also http://bit.ly/1F6WBVD

thanks

Page 131: Tour of language landscape (code.talks)

see also http://bit.ly/1F6WBVD

I’m done, here you go

Page 132: Tour of language landscape (code.talks)

see also http://bit.ly/1F6WBVD

thanks

Page 133: Tour of language landscape (code.talks)

see also http://bit.ly/1F6WBVD

immutable by default

Page 134: Tour of language landscape (code.talks)

fn take(v : &Vec<i32>) { v.push(5); }

let v = vec![]; take(&v); // cannot borrow immutable borrowed // content `*v` as mutable // v.push(5); // ^

see also http://bit.ly/1F6WBVD

Page 135: Tour of language landscape (code.talks)

fn take(v : &mut Vec<i32>) { v.push(5); }

let mut v = vec![]; take(&mut v);

println!("v[0] is {}", v[0]); // v[0] is 5

see also http://bit.ly/1F6WBVD

Page 136: Tour of language landscape (code.talks)

borrowing rules

see also http://bit.ly/1F6WBVD

Page 137: Tour of language landscape (code.talks)

see also http://bit.ly/1F6WBVD

Rule 1.the borrower’s scope must not

outlast the owner

Page 138: Tour of language landscape (code.talks)

see also http://bit.ly/1F6WBVD

Rule 2.one of the following, but not both:

2.1 0 or more refs to a resource 2.2 exactly 1 mutable ref

Page 139: Tour of language landscape (code.talks)

see also http://bit.ly/1F6WBVD

data race

There is a ‘data race’ when two or more pointers access the same memory location at the same time, where at least one of them is writing, and

the operations are not synchronised.

Page 140: Tour of language landscape (code.talks)

see also http://bit.ly/1F6WBVD

data race

a. two or more pointers to the same resourceb. at least one is writingc. operations are not synchronised

Page 141: Tour of language landscape (code.talks)

see also http://bit.ly/1F6WBVD

Data Race Conditionsa. two or more pointers to the same resourceb. at least one is writingc. operations are not synchronised

Borrowing Rulesone of the following, but not both:

2.1 0 or more refs to a resource 2.2 exactly 1 mutable ref

Page 142: Tour of language landscape (code.talks)

see also http://bit.ly/1F6WBVD

Data Race Conditionsa. two or more pointers to the same resourceb. at least one is writingc. operations are not synchronised

Borrowing Rulesone of the following, but not both:

2.1 0 or more refs to a resource 2.2 exactly 1 mutable ref

Page 143: Tour of language landscape (code.talks)

see also http://bit.ly/1F6WBVD

Page 144: Tour of language landscape (code.talks)
Page 145: Tour of language landscape (code.talks)

Dependent Types

Uniqueness Types

Bit Syntax

Borrowed Pointers

Type Provider Pipes

Statically Resolved TP Implicit Interface Implementation

Signals

Macros

Unit-of-Measure

Actor Model

Page 146: Tour of language landscape (code.talks)

seen generics?aka parametric polymorphism

Page 147: Tour of language landscape (code.talks)

List<T>

Page 148: Tour of language landscape (code.talks)

List<T>List<int> List<Cat>

List<string>

Page 149: Tour of language landscape (code.talks)

what if…

Page 150: Tour of language landscape (code.talks)

types that depend on arbitrary values?

Page 151: Tour of language landscape (code.talks)

Vect n avector of n elements of type a

Page 152: Tour of language landscape (code.talks)

zipWith : (a -> b -> c) -> Vect n a -> Vect n b -> Vect n c

Page 153: Tour of language landscape (code.talks)

zipWith f [] [] = [] zipWith f (x :: xs) (y :: ys) = f x y :: zipWith f xs ys

Page 154: Tour of language landscape (code.talks)

Type Driven Development

Page 155: Tour of language landscape (code.talks)

making invalid state UNREPRESENTABLE

Page 156: Tour of language landscape (code.talks)

see also https://vimeo.com/123606435

Page 157: Tour of language landscape (code.talks)
Page 158: Tour of language landscape (code.talks)

Signals

Dependent Types

Uniqueness Types

Bit Syntax

Borrowed Pointers

Type Provider Pipes

Statically Resolved TP Implicit Interface Implementation

Macros

Unit-of-Measure

Actor Model

Page 159: Tour of language landscape (code.talks)

Functional Reactive Programming

Page 160: Tour of language landscape (code.talks)

Value over Time

Page 161: Tour of language landscape (code.talks)

Time

Value

Page 162: Tour of language landscape (code.talks)

Signals

Page 163: Tour of language landscape (code.talks)

Move Up

Move Down

Page 164: Tour of language landscape (code.talks)

private var arrowKeyUp:Bool; private var arrowKeyDown:Bool;

private var platform1:Platform; private var platform2:Platform; private var ball:Ball;

Page 165: Tour of language landscape (code.talks)

function keyDown(event:KeyboardEvent):Void { if (currentGameState == Paused && event.keyCode == 32) { setGameState(Playing); } else if (event.keyCode == 38) {

arrowKeyUp = true; }else if (event.keyCode == 40) {

arrowKeyDown = true; } }

Page 166: Tour of language landscape (code.talks)

function keyUp(event:KeyboardEvent):Void { if (event.keyCode == 38) {

arrowKeyUp = false; } else if (event.keyCode == 40) {

arrowKeyDown = false; } }

Page 167: Tour of language landscape (code.talks)

function everyFrame(event:Event):Void { if(currentGameState == Playing){ if (arrowKeyUp) { platform1.y -= platformSpeed; } if (arrowKeyDown) { platform1.y += platformSpeed; } if (platform1.y < 5) platform1.y = 5; if (platform1.y > 395) platform1.y = 395; } }

Page 168: Tour of language landscape (code.talks)

function everyFrame(event:Event):Void { if(currentGameState == Playing){ if (arrowKeyUp) { platform1.y -= platformSpeed; } if (arrowKeyDown) { platform1.y += platformSpeed; } if (platform1.y < 5)

platform1.y = 5;if (platform1.y > 395)

platform1.y = 395; } }

Page 169: Tour of language landscape (code.talks)

source files

state changes

Page 170: Tour of language landscape (code.talks)

source files execution

Page 171: Tour of language landscape (code.talks)

source files execution

Page 172: Tour of language landscape (code.talks)

mental model

input state new state behaviour

{ x; y } { x; y-speed }

{ x; y } { x; y+speed }

timer { x; y } { x; y } draw platform

… … … …

Page 173: Tour of language landscape (code.talks)

transformation

let y = f(x)

Imperative Functional

x.f()

mutation

Page 174: Tour of language landscape (code.talks)

transformations simplify problem

decomposition

Page 175: Tour of language landscape (code.talks)

Move Up

Move Down

Page 176: Tour of language landscape (code.talks)

type alias Platform = {x:Int, y:Int} defaultPlatform = {x=5, y=0}

delta = Time.fps 20 input = Signal.sampleOn delta Keyboard.arrows

cap x = max 5 <| min x 395

p1 : Signal Platform p1 = foldp (\{x, y} s -> {s | y <- cap <| s.y + 5*y}) defaultPlatform input

Page 177: Tour of language landscape (code.talks)

type alias Platform = {x:Int, y:Int}defaultPlatform = {x=5, y=0}

delta = Time.fps 20 input = Signal.sampleOn delta Keyboard.arrows

cap x = max 5 <| min x 395

p1 : Signal Platform p1 = foldp (\{x, y} s -> {s | y <- cap <| s.y + 5*y}) defaultPlatform input

Page 178: Tour of language landscape (code.talks)

type alias Platform = {x:Int, y:Int} defaultPlatform = {x=5, y=0}

delta = Time.fps 20 input = Signal.sampleOn delta Keyboard.arrows

cap x = max 5 <| min x 395

p1 : Signal Platform p1 = foldp (\{x, y} s -> {s | y <- cap <| s.y + 5*y}) defaultPlatform input

Page 179: Tour of language landscape (code.talks)

Keyboard.arrowsUP { x=0, y=1 } DOWN { x=0, y=-1 } LEFT { x=-1, y=0 } RIGHT { x=1, y=0 }

Page 180: Tour of language landscape (code.talks)

type alias Platform = {x:Int, y:Int} defaultPlatform = {x=5, y=0}

delta = Time.fps 20 input = Signal.sampleOn delta Keyboard.arrows

cap x = max 5 <| min x 395

p1 : Signal Platformp1 = foldp (\{x, y} s -> {s | y <- cap <| s.y + 5*y}) defaultPlatform input

Page 181: Tour of language landscape (code.talks)

type alias Platform = {x:Int, y:Int} defaultPlatform = {x=5, y=0}

delta = Time.fps 20 input = Signal.sampleOn delta Keyboard.arrows

cap x = max 5 <| min x 395

p1 : Signal Platform p1 = foldp (\{x, y} s -> {s | y <- cap <| s.y + 5*y}) defaultPlatform input

Page 182: Tour of language landscape (code.talks)

type alias Platform = {x:Int, y:Int} defaultPlatform = {x=5, y=0}

delta = Time.fps 20 input = Signal.sampleOn delta Keyboard.arrows

cap x = max 5 <| min x 395

p1 : Signal Platform p1 = foldp (\{x, y} s -> {s | y <- cap <| s.y + 5*y}) defaultPlatform input

Page 183: Tour of language landscape (code.talks)

type alias Platform = {x:Int, y:Int} defaultPlatform = {x=5, y=0}

delta = Time.fps 20 input = Signal.sampleOn delta Keyboard.arrows

cap x = max 5 <| min x 395

p1 : Signal Platform p1 = foldp (\{x, y} s -> {s | y <- cap <| s.y + 5*y}) defaultPlatform input

Page 184: Tour of language landscape (code.talks)

“I thought of objects being like biological cells and/or

individual computers on a network, only able to

communicate with messages.”

- Alan Kay

Page 185: Tour of language landscape (code.talks)

“OOP to me means only messaging, local retention and protection and hiding of state-

process, and extreme late-binding of all things.”

- Alan Kay

Page 186: Tour of language landscape (code.talks)
Page 187: Tour of language landscape (code.talks)

Borrowed Pointers

Actor Model

Bit Syntax

Type Provider Pipes

Statically Resolved TP Implicit Interface Implementation

Dependent Types

Uniqueness Types

Signals

Macros

Unit-of-Measure

Page 188: Tour of language landscape (code.talks)

actor model

Page 189: Tour of language landscape (code.talks)

actor

state mailbox

Page 190: Tour of language landscape (code.talks)

actors share nothing

Page 191: Tour of language landscape (code.talks)

actor

state mailboxactor

Page 192: Tour of language landscape (code.talks)

actor

state mailboxactor

Page 193: Tour of language landscape (code.talks)

processingstorage

communication

Page 194: Tour of language landscape (code.talks)

loop (Map) -> receive {get, Key, Pid} -> Pid ! maps:get(Key, Map, not_found), loop(Map); {set, Key, Value} -> loop(maps:put(Key, Value, Map)) end.

Page 195: Tour of language landscape (code.talks)

loop (Map) -> receive {get, Key, Pid} -> Pid ! maps:get(Key, Map, not_found), loop(Map); {set, Key, Value} -> loop(maps:put(Key, Value, Map)) end.

Page 196: Tour of language landscape (code.talks)

loop (Map) -> receive {get, Key, Pid} -> Pid ! maps:get(Key, Map, not_found), loop(Map); {set, Key, Value} -> loop(maps:put(Key, Value, Map)) end.

Page 197: Tour of language landscape (code.talks)

loop (Map) -> receive {get, Key, Pid} -> Pid ! maps:get(Key, Map, not_found), loop(Map); {set, Key, Value} -> loop(maps:put(Key, Value, Map)) end.

Page 198: Tour of language landscape (code.talks)

client (N, Pid) -> Pid ! {set, N, N}, Pid ! {get, N, self()}, receive not_found -> io:format(“~p :-(~n”, [N]); N -> io:format(“~p :-)~n”, [N]); _ -> io:format(“~p …~n”, [N]) end.

Page 199: Tour of language landscape (code.talks)

client (N, Pid) -> Pid ! {set, N, N}, Pid ! {get, N, self()}, receive not_found -> io:format(“~p :-(~n”, [N]); N -> io:format(“~p :-)~n”, [N]); _ -> io:format(“~p …~n”, [N]) end.

Page 200: Tour of language landscape (code.talks)

client (N, Pid) -> Pid ! {set, N, N}, Pid ! {get, N, self()}, receive not_found -> io:format(“~p :-(~n”, [N]); N -> io:format(“~p :-)~n”, [N]); _ -> io:format(“~p …~n”, [N]) end.

Page 201: Tour of language landscape (code.talks)

start(N) -> Kvs = spawn(mod, loop, [#{}]), [spawn(mod, client, [X, Kvs]) || X <- lists:seq(1,N)].

Page 202: Tour of language landscape (code.talks)
Page 203: Tour of language landscape (code.talks)

actors are cheap

Page 204: Tour of language landscape (code.talks)

no locks!

Page 205: Tour of language landscape (code.talks)

need state?talk to the actor!

Page 206: Tour of language landscape (code.talks)

location transparency

Page 207: Tour of language landscape (code.talks)

pre-emptive scheduling

Page 208: Tour of language landscape (code.talks)

makes you THINK

about distributed systems

Page 209: Tour of language landscape (code.talks)

messaging promotes failure thinking

Page 210: Tour of language landscape (code.talks)

Distributed

Computing

Page 211: Tour of language landscape (code.talks)

Network is reliableLatency is zero

Bandwidth is infiniteNetwork is secure

Topology doesn't changeThere is one administrator

Transport cost is zeroThe network is homogeneous

8 fallacies of distributed computing

Page 212: Tour of language landscape (code.talks)

supervise & restart

Page 213: Tour of language landscape (code.talks)

Type Provider Pipes

Statically Resolved TP Implicit Interface Implementation

Borrowed Pointers Dependent Types

Uniqueness TypesOTP

Bit SyntaxSignals

Macros

Unit-of-Measure

Page 214: Tour of language landscape (code.talks)

10,000 hours to be good at something

see also http://bit.ly/1KN7SLq

Page 215: Tour of language landscape (code.talks)

10,000 hours to be good at something

see also http://bit.ly/1KN7SLq

Page 216: Tour of language landscape (code.talks)

10,000 hours to reach top of an ultra-

competitive field

see also http://bit.ly/1KN7SLq

Page 217: Tour of language landscape (code.talks)
Page 218: Tour of language landscape (code.talks)

the first 20 hours - how to learn anything

see also http://bit.ly/1KN7SLq

Page 219: Tour of language landscape (code.talks)

Practice Time

How

goo

d yo

u ar

e

see also http://bit.ly/1KN7SLq

Page 220: Tour of language landscape (code.talks)

1.Deconstruct the skill

see also http://bit.ly/1KN7SLq

Page 221: Tour of language landscape (code.talks)

1.Deconstruct the skill2.Learn enough to self-correct

see also http://bit.ly/1KN7SLq

Page 222: Tour of language landscape (code.talks)

1.Deconstruct the skill2.Learn enough to self-correct3.Remove practice barriers

see also http://bit.ly/1KN7SLq

Page 223: Tour of language landscape (code.talks)

1.Deconstruct the skill2.Learn enough to self-correct3.Remove practice barriers4.Practice at least 20 hrs

see also http://bit.ly/1KN7SLq

Page 224: Tour of language landscape (code.talks)
Page 225: Tour of language landscape (code.talks)

learn a new paradigmnot a new syntax

see also http://bit.ly/1IzXVSo

Page 226: Tour of language landscape (code.talks)

logic programming

Page 227: Tour of language landscape (code.talks)

stack-oriented programming

Page 228: Tour of language landscape (code.talks)

array programming

Page 229: Tour of language landscape (code.talks)

“A language that doesn't affect the way you think

about programming, is not worth knowing.”

- Alan Perlis

Page 230: Tour of language landscape (code.talks)

see also http://bit.ly/1IzXVSo

Page 231: Tour of language landscape (code.talks)

see also http://bit.ly/1IzXVSo

Page 232: Tour of language landscape (code.talks)

“Learning is an act of creation itself, because something

happens in you that wasn't there before.”

- Alan Kay

Page 233: Tour of language landscape (code.talks)

@theburningmonktheburningmonk.comgithub.com/theburningmonk