A Look Into the Future
summary
Kotlin 1.4 emphasizes quality and performance and continues work on Kotlin Multiplatform Mobile to share code between Android and iOS; JVM interoperability targets Records and Sealed Classes so Java APIs (and Project Loom) work out of the box. Community tracking uses YouTrack and KEEP; callable-reference changes had ~70 votes and function interfaces (200 votes) lands as a solved SAM problem in 1.4. Proposals like a ternary operator (80 votes) are declined; ideas under exploration include namespace extensions, decorators, value‑based classes to replace inline class naming ahead of Java Valhalla, and compiler plugins (e.g. Jetpack Compose @Composable, differentiable programming). Recording brought to you by American Express.
AI-written summary · about
chapters (27)
- 0:00Intro
- 0:15A bit of history
- 1:14Sharing code
- 1:36JVM server/interoperability
- 1:52Java interoperability: upcoming
- 2:38Driving forces
- 3:41YouTrack vs KEEP
- 4:34YouTrack: language design
- 7:11KT-11968: Statically accessible extensions
- 9:26Similar/related problem
- 10:27What is object?
- 11:23Just a namespace?
- 11:52Enables: companion namespaces
- 12:18Enables: namespaces extensions
- 13:51Member extensions
- 14:31KT-10468: Multiple receivers
- 15:37Syntactic analogy
- 16:24Take it further
- 19:16Decorators with receivers
- 22:37Ternary operator
- 27:00Mutable data
- 29:13Can we have cake and eat it, too?
- 33:31Stable future for experimental inline classes
- 38:14Growing community
- 38:49Conclusion
- 38:59Recap
- 39:20What else we are looking at?
