Adventure with Types in Haskell - Simon Peyton Jones (Lecture 1)

Recorded at Oregon Programming Languages Summer School 2013. www.cs.uoregon.edu/research/s...
Lecture 1 Slides: www.cs.uoregon.edu/research/s...
System F in GHC: www.cs.uoregon.edu/research/s...
Kinds and GADTs: www.cs.uoregon.edu/research/s...
Type Inference: www.cs.uoregon.edu/research/s...
Fun with Type Functions: www.cs.uoregon.edu/research/s...

[@gfixler]

I'm sad to learn that I'll never invent a time machine, because if I ever will have were to, the first thing I would will have had done is go back in time and choke out the camera operator, point the camera at the screen, and not touch it again for the entire lecture.

[@ephrion7832]

gfixler 1:16:00 I WANT TO SEE HIS FACE EVEN MORE CLEARLY

[@aaronhall8039]

Well, he does use the whiteboard a bit - and the slides are here: www.cs.uoregon.edu/research/summerschool/summer13/lectures/ClassesJimOPLSS.pdf

[@olivertirreg]

Even if. The camara movement is annoying. Skip the whiteboard part better. A professional would film the slides and switch to the board iff Simon is using it.

[@fp2671]

i think it's in keeping with the Haskell spirit to have a really interesting lecture with horrifically bad production standards.

[@mcspud]

Lost it haha

[@ha.alamin]

Everyone's complaining about the camerawork, but to me, the far more jarring problem is the microphone constantly cutting out in blips.

[@morthim]

the static was immutable.

[@mayabartolabac]

i get used to that and my brain fills in the gaps

[@NicholasShanks]

The cameraman is also responsible for the microphone. People complaning about the recording are mostly referring to the audio.

[@anthony7194]

My own personal hell is this camera man recording anything I want to watch.

[@collinrea6183]

Even on a bad recording I could watch Simon Peyton Jones lecture every day

[@Harrichael]

Plot twist: the camera man is automated software written by Simon on the way to the lecture.

[@miscibi]

OMG, thank you for that! You made my day. I almost died from laughing my ass off! :D

[@Evan490BC]

So, he didn't use Control.Monad.Fail?

[@charvakpatel962]

He is so passionate, I love this kind of people. I would love to discuss various things with them for years. I have met only one person who is this passionate in real life.

[@benjamingeiger]

Incidentally, one of the few people I've known who was this passionate in real life was also a programming languages researcher. I put in more work in his classes than any of the other classes I took in grad school (including the ones related to my own specialization) but I learned more in those classes...

[@jasbrg]

those close ups around 1:17:00 though

[@cockneykevin]

I like how the camera seems to capture exactly where I would look if I were in class. Seriously.

[@jesseschalken6322]

It's so depressing that such an important lecture hasn't been recorded properly. :(

[@JohnBastardSnow]

To me the camera operator is pretty good. I like how s/he quickly switches between relevant things. I like it this way.

[@flesh140]

I came for the lecture topic, but I stayed for the comments about the horrific camera work...

[@Ancipital_]

Great lecture, I revisit it every now and then. Also that camera work is stunning! LOL i'm not even kidding!

[@carolsmall992]

SPJ is a superb communicator - so it's incredibly frustrating that the camera person completely ruined this talk.

[@FruchteisMitErdbeer]

This is such a good lecture. The students are very perceptive, and lots of deeply rooted tradeoffs in language design get explored here. Peyton Jones' speculations regarding parametric polymorhpism in newer languages is specially interesting considering developements in Rust, Swift and other modern languages. They are clealy inspired by these considerations

[@odyxanthi]

The camera work has made this impossible to watch unfortunately...

[@griof]

1:16:50 what a dramatic shot!

[@ConstellationMovies]

If you have an equalizer installed you can drop 14khz to 0, and significantly reduce ~1k and ~4k, the buzzing and hissing will go away but be warned it'll sound _pretty_ muffled. still better than all these artifacts IMO

[@SergiiStarodubtsev]

just brilliant !

[@triggerhappy9552]

Anyone know if he gave this lecture somewhere else with a better recording?

[@_ranko]

Maybe I'm pulling it from nowhere but 16:34 was an amazing Garbage-collected Object-oriented Language joke lmao

[@declup]

SPJ, what a mensch.

[@shruti9845]

Feels like Gordon Ramsey teaching type system

[@pkcc9381]

Awesome talk but had headache with the camera moments.

[@davidyanceyjr]

I just noticed at 42:14 he's not wearing shoes....

[@EnricoPolanski]

7:30, I'm already lost at the filter function, when he asks if everything's clear, I'm like "wtf?".

[@cellularmitosis2]

Such a shame about the audio quality and camerawork

[@mirkeau]

"What could be easier than that??" 😱💕

[@MantasGee]

This doesn't seem to type check: instance Typeable a => Typeable [a] where typeRep _ = TR "List" [ typeRep (undefined :: a) ]

[@brianevans4]

running a startup on haskell. imagine the next airbnb uses haskell

[@mynamebestname]

would be nice if some clever guy/girl could clean up the sound in this video, I guess it just requires some simple applied DSP techniques

[@christianbrolin1482]

At 34:45 Simon talks about the coolest example of type classes. A similar, but simpler example is, I think, the Eq class with an instance for Bool functions, i.e. functions from Bool: {-# LANGUAGE FlexibleInstances #-} instance Eq a => Eq (Bool -> a) where f == g = f True == g True && f False == g False Now you can compare (a subset of) functions! *Main> not . not == id True or *Main> not == const False False But why is this cool? Because this Eq instance allows equality check of any number of Bool arguments, e.g.: *Main> (&&) == (||) False Sometimes it is even useful: *main> let xor a b = nand (nand a c) (nand b c) where c=nand a b *Main> (/=) == xor True But be careful, with too many arguments it will be slow. In the worst case it evaluates every combinations, i.e. 2^n tests

[@christianbrolin1482]

*Main> let nand a b = not (a && b)

[@ulstulst]

Camera work needs a bit of work, too much movement. Otherwise A+ stuff

[@jeffrey9851]

The noise is really the problem.

[@Steven676]

Who knew that the Monty Python lumberjack also wrote a programming language.

[@RedSkyHorizon]

Stephen Hawking is cameraman

[@dengan699]

I almost vomit from camera moves 😒😒

[@enricolumetti1995]

Why is he barefoot?

[@iNuchalHead]

Shoes these days aren't purely functional... I guess they're not really imperative either.

[@leonardomoraes6505]

1:16:45 wtf

[@leonardomoraes6505]

1:17:11 WTF

[@alexanderskladovski]

Why he is barefoot?

[@sarahkerrigan7240]

Wow,there's a girl in the class !

[@acortis]

for the love of ... stop moving the camera!

[@Voltra_]

Fucking static noise