Closing Panel
summary
Panel summarizes concrete plans and status: Kotlin team size is about 50 people; Java 9 support lands across 1.1/1.2; Kotlin/Native targets LLVM; a Gradle Kotlin DSL Q1 2018 rollout is planned and can be adopted incrementally; coroutines are described as complementary to Rx rather than a drop-in replacement; JetBrains integrates Kotlin heavily into IntelliJ/Android Studio and experiments with neural completion for smarter code suggestions; an education plugin and kotlinx libraries for common IO, dates and serialization are underway, and Java compatibility remains a priority.
AI-written summary · about
chapters (38)
- 0:00Intro
- 1:00Introductions
- 2:10Audience Questions
- 3:20Java Compatibility
- 5:05Code Sharing
- 6:35Java 9 Support
- 9:30Cost of Kotlin
- 10:30Gradle to Kotlin
- 12:30Native Kotlin support
- 14:15Kotlin reflection
- 16:25Off heap storage
- 17:00Common platform
- 17:35Common libraries
- 18:20IP
- 18:55Dr Cook
- 19:15Will Kotlin become a teaching language
- 20:00Some schools are teaching Kotlin
- 20:20Kotlin education plugin
- 20:40Foundation to host Kotlin
- 21:00Foundation structure
- 23:40Questions
- 25:10Decompile
- 25:35Functional Programming
- 27:55Java vs Kotlin
- 28:30Language Features
- 30:45Cutting
- 31:20Rx is dead
- 31:45Switching to Coroutines
- 33:25Will Coroutines Replace
- 35:10Kotlin or Java
- 36:15Lessons from Scala and Swift
- 37:10Lessons from Scala
- 38:55Google buying JetBrains
- 40:50Google and JetBrains
- 41:35Kotlin independence
- 41:55Kotlin complexity
- 42:45Things you leave out
- 44:00Question
