Mr. Kotlin VS. Mr. Java, an inspirational parody!
summary
Claims that Java 21 virtual threads beat coroutines are contrasted with concrete examples: Kotlin uses structured coroutines and compile‑time null safety (the Elvis operator) and shows a two‑day multiplatform UI prototype that runs on JVM, Android and JS. Presenters cite “three billion devices” for both Java and Kotlin/Android, note Gradle’s Kotlin DSL and Google’s smooth Kotlin adoption with fewer bugs, and demo live code comparing thread footprints, compile errors for nullable fields, and practical migration steps.
AI-written summary · about
chapters (14)
- 0:00Introduction to the rivalry
- 1:53Speakers’ backgrounds
- 4:51Java vs Kotlin overview
- 7:17Java 21 and Project Loom
- 11:12Kotlin coroutines vs Java threads
- 14:25Kotlin ecosystem growth
- 16:34Java’s origin story
- 17:57Kotlin’s quirky history
- 19:07Ecosystem and libraries
- 20:11Null safety in Kotlin
- 21:57Records and encapsulation
- 24:04Kotlin multiplatform
- 27:38Java vs Kotlin popularity
- 30:50Audience reactions and Q&A
related talks
36mJava vs. Kotlin: The Ultimate Showdown of Virtual Threads & Coroutines
44mAsync Showdown: Java Virtual Threads vs. Kotlin Coroutines
39mVirtual Threads vs. Coroutines in 2026: Is Java Finally There?
49mAn Introduction to Kotlin
01h 02mFarewell Kotlin, welcome new Java
50mAsync Showdown: Java Virtual Threads vs. Kotlin Coroutines
48mKotlin Against Everyone
58mGroovy, Java, and Kotlin