What a Java Developer Can Learn from Haskell?
summary
Compares specific Haskell ideas to Java practices: argues that static strong typing improves readability and early error detection, shows IntelliJ structural search can find methods by signature similar to Haskell lookup, and critiques Java 8 Optionals as incomplete while presenting Kotlin’s compile-time null-safety as a working alternative. Demonstrates that immutable data models scale in real systems by citing Datomic, Git, and John Carmack’s immutable-style game snapshots to achieve consistent saving/state without locking.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 2:08Type systems
- 5:18Static strong typing benefits
- 10:48String-only type problem
- 12:58Java exceptions limits
- 15:21Null history and issues
- 19:55Optional types in Kotlin
- 26:41Immutability benefits
- 33:42Value Objects and DDD
- 36:12Immutable data structures
- 40:18State persistence in immutable world
- 43:54Summary
related talks
01h 02mHaskell for Java Programmers
34mPrinciples of functional programming with examples in Java and Haskell
01h 02mFarewell Kotlin, welcome new Java
56mJava Sucks (So C# Didn't Have To)
57mWhat a Java Developer Can Learn from Golang?
01h 03mHow Kotlin makes your Java code better
01h 12mThe Power of JVM Language
44mTyping in Java, Kotlin and Scala