Let's get functional
summary
Argument that functional ideas (immutability, pure functions, no side effects) make Java 7 Android code smaller, more predictable and easier to test, demonstrated with concrete rewrites: a hand-rolled word-count becomes a groupBy + map to pairs one-liner, list folding replaces loops to fold to sum a basket, and filtering/mapping composes for sorting and thresholds. Recommends tools and languages to apply this now: RxJava, AutoValue, Retrolambda, Kotlin and incremental migration from imperative code.
AI-written summary · about
chapters (8)
- 0:00Start
- 2:42What's the point?
- 7:59Pure functions
- 9:05You can use most common languages
- 17:34What is your data?
- 20:52Fold?
- 24:14Start small
- 27:23Good reads
related talks
36mHow functional programming change my Java code
34mFunctional Android
37mPragmatic Functional Refactoring with Java 8
34mFunctional Programming in Kotlin for AndroidDevs
27mWhy Kotlin is my favourite example of Functional Programming?
41mArchitectures Using Functional Programming Concepts
48mKotlin & Functional Programming: pick the best, skip the rest
51mFrom Java 7 to Functional Programming
