Why Functional Programming Matters • John Hughes • YOW! 2017

This presentation was recorded at YOW! 2017. #GOTOcon #YOW
yowcon.com
John Hughes - Functional Programming Enthusiast
ABSTRACT
In 1990 I published “Why Functional Programming Matters”, a manifesto for FP-but the subject is much older than that! In this talk I’ll take a deep dive into its history, highlighting some of the classic papers of the subject, personal favourites, and some of my own work. At the end of the day, four themes emerge that characterize what I love about the subject.
John Hughes has been a functional programming enthusiast for more than thirty years, at the Universities of Oxford, Glasgow, and since 1992 Chalmers University in Gothenburg, Sweden. He served on the Haskell design committee, co-chairing the committee for Haskell 98, and is the author of more than 75 papers, including “Why Functional Programming Matters“, one of the classics of the area. With Koen Claessen, he created QuickCheck, a property based testing tool for Haskell. It has become the defacto testing tool for FP and more recently for many other languages. In 2006 he founded Quviq to commercialise the technology for Erlang and C - Testing the Hard Stuff and Staying Sane. [...]
RECOMMENDED BOOKS
Richard Feldman • Elm in Action • amzn.to/387kujI
Jeremy Fairbank • Programming Elm • amzn.to/2WhZCE8
Wolfgang Loder • Web Applications with Elm • amzn.to/3jblQ3q
Cristian Salcescu • Functional Programming in JavaScript • amzn.to/3y75jBS
/ gotocon
/ goto-
/ gotoconferences
#FunctionalProgramming #FP #Haskell #Programming #JohnHughes #Quviq #YOWcon
Looking for a unique learning experience?
Attend the next GOTO conference near you! Get your ticket at gotopia.tech
Sign up for updates and specials at gotopia.tech/newsletter
SUBSCRIBE TO OUR CHANNEL - new videos posted almost daily.
kzbin.info...

[@teial]

Fantastic talk! Get right to the heart of the question of why we need FP.

[@devagr]

Just wanted to say I am absolutely loving the YOW uploads, thank you very much, it would have been a shame if all this amazing content never hit the internet.

[@amonowyful]

Awesome talk, thanks! For anyone interested in Backus paper but too rookie to read it, check Eric Normands podcast about it where he reads parts of it and adds explanation

[@KennethBoneth]

Interesting to look at the development times in the table at 33:19 as well. Lisp having a 3 hour development time. and only 12 lines of documentation. Whereas haskell had 465 lines of documentation.

[@ericpmoss]

It would be fun to see the implementations and see what could be improved with each. It has been a decade since I read the paper, but IIRC, the Lisp team finished first and the code worked, with many of the other attempts not working error-free. That would leave 5 hours at least to work on the algorithm.

[@Nellak2011]

Beautiful ❤