Closing Panel
summary
Fourteen panelists answer audience and online questions about concrete things not slogans they report a 700 person waiting list for k2 and reveal 1 300 mascot pins Cody exists they describe work on compose multi-platform and compose desktop as promising but exploratory note JS IR compile times are currently slow explain Kotlin notebooks are usable for data work and mention specific libraries and JVM gRPC protobuf support discuss Loom interoperability with coroutines and debate removing or replacing companion objects and other language specifics.
AI-written summary · about
chapters (38)
- 0:00Closing panel welcome
- 0:43Panelists introduced
- 3:53Kotlin replacing other languages?
- 5:38Kotlin in gaming and simulations
- 7:05Kotlin and Dart for Flutter
- 9:13Kotlin 2.0 features to remove
- 11:02Compose for Desktop future
- 12:52Kotlin Multiplatform barriers
- 16:28Java threat to Kotlin?
- 19:40Functional vs object-oriented preferences
- 20:22Default formatter in compiler
- 21:48Kotlin mascot update
- 23:13Most important Kotlin platform in five years
- 24:39Slack’s shift from gaming to chat
- 26:04Kotlin for data science
- 27:09Kotlin/JS IR compilation issues
- 28:54Kotlin language design approach
- 30:59Kotlin in backend apps
- 32:23Compose for Web/WASM future
- 34:11iOS devs with Kotlin
- 34:54Virtual threads and coroutines
- 37:04Why coroutines not named with K
- 37:47Kotlin scripts for automation
- 38:54Teaching Kotlin to kids
- 41:46Kotlin for Minecraft modding
- 42:06Compose for Desktop without JVM
- 42:49Kotlin Multiplatform UI guidelines
- 43:54Reflection in multiplatform
- 44:59User success with Kotlin
- 45:45Function coloring in Kotlin
- 48:58Why AppCode killed
- 49:39Kotlin SDKs for GCP
- 50:23Google’s multiplatform libraries
- 51:47Live code evaluation in debugger
- 53:53Kotlin notebooks and debugging
- 54:13JetBrains Gateway performance
- 54:57Will AI replace devs?
- 55:39Kotlin’s new mascot Cody
