10 things a Scala developer feels when coming back to Java
summary
Compares practical trade-offs when moving from Scala back to Java: Lombok reduces boilerplate but obscures generated code; Spring Cloud gives service discovery and circuit-breakers to speed delivery; Spring Data can generate CRUD endpoints in a few lines. Also lists pains in Java: Java 8 streams are verbose for small collections, Optionals proliferate, AOP/transactional annotations create fragile runtime behavior and hard-to-test integrations, slow compile-plus-container reload cycles, and lack of ADTs/pattern matching/implicits (partly mitigated by Vavr) increases runtime error risk.
AI-written summary · about
chapters (19)
- 0:00Return to Java intro
- 1:27Java evolution since 2004
- 3:53Scala discovery and return
- 4:58Java vs Scala philosophy
- 6:20JavaBeans constraints impact
- 8:08Java 8 lambdas and defaults
- 9:10Streams and collectors
- 11:38Exceptions and lambdas handling
- 12:21Annotations: Lombok and Spring
- 15:28Interceptors and runtime
- 17:39Integration tests
- 18:40Compiler and code trust
- 20:47JPA and modern injection
- 24:01Java exceptions issues
- 26:49Vavr functional relief
- 29:37Java vs Scala gaps
- 34:10Fast compile vs trust
- 36:14Conclusion
- 36:39Q&A
