My First Experience With Functional Programming

Personal experience on functional programming

Transcript

1. λ
2. My Experience with Functional Programming Arkar Min Aung iOS Dev (Nex)
3. Actually, I am a complete n00b in FP Please excuse me if I say some stuffs wrong
4. WHAT IS Functional Programming?
5. Imperative Programming Telling the machine HOW to do something, and as a result what you want to happen will happen.
6. Declarative Programming Telling the machine WHAT you would like to happen, and let the computer figure out how to do it.
7. Functional Programming != Functional Programming Language
8. Functional Programming is inspired by Mathematics
9. Everything is a function (x) = x+2 (x) = sin(x)
10. Values are “Immutable”
11. If, y = sin (x) and, x = π y = sin (π) It does not make sense to do x = x + 1 you cannot change the state of x
12. Functions without side-effects
13. Referential Transparency
14. Functions are first class citizens
15. Higher Order Functions Functions which take other functions as args e.g differential -> d/dx (x^2) = 2x
16. WHY Functional Programming?
17. My friend introduced me “Bro, this thingy called FP is sooo awesome that it will blow your mind on many levels”
18. Curious
19. I love Mathematics I love it when a language gives me Integer size which can grow as big as the resources allow
20. – Alan J. Perlis “A language which does not change the way you think is not a language worth learning.”
21. – Alan J. Perlis “A programming language is low level when its programs require attention to the irrelevant.”
22. So what lang did I choose to learn FP? A programming language should just be a tool for you to complete some task. There is no point fighting over what is better and what is not.
23. Haskell
24. Recursion To iterate is human, to recurse divine
25. Oh yeah! Recursions • GNU • GNU is Not Unix • ((GNU is Not Unix)NU) is Not Unix • …
26. Pattern Matching
27. Purity
28. Lazy
29. • Args to a function are evaluated only when needed for the computation. • Very useful for dealing with very large or infinite streams of data. • Opposite to eager evaluation
30. Concurrent
31. So • Imperative Languages: • Efficient execution • Complex syntax • Concurrency is programmer designed • Functional Languages: • Inefficient execution • Simple syntax • Programs can automatically be made concurrent
32. My sole purpose
33. :) Thank you so much
34. λ @ark_aung @khzaw Ko Thura Hlaing github - trhura
35. Questions please? or comments? Even if you don’t get stuffs in this talk, it is my fault for not being able to explain better. Please don’t feel bad.