Kotlin: Boring Languages are dead Long Live Boring Languages
summary
Argues Kotlin becomes the pragmatic “boring” default for JVM and Android because its type system gives null-safety via nullable types and smart casting, shows a concrete Android example using lateinit to avoid framework-induced null checks, and notes Kotlin compiles to JVM/JS/native so migration is practical. Warns that adding Arrow/Option-style patterns increases complexity and causes brittle API changes (maybe-to-nonmaybe refactors), and that runtime NPEs can still occur when JVM interop or initialization order slips.
AI-written summary · about
chapters (31)
- 0:00Intro
- 1:12Code on Mars
- 2:46I like Kotlin
- 3:49Tayobi
- 5:08Kotlin
- 5:57Programming languages
- 6:21Best practices
- 8:15Boring languages
- 8:45Project failures
- 9:18Tradeoffs
- 16:42Why Kotlin
- 18:50The billion dollar mistake
- 19:32Java Optional
- 21:08Kotlin Nulls
- 22:43Swift Nulls
- 23:24Smart Casting
- 24:02Typescript
- 25:07Kotlin type system
- 26:52Late init
- 27:10Spring Context
- 28:40The Problem
- 29:22Latent
- 29:59Android
- 30:51Android System
- 31:57Awesome Type System
- 32:59Option Type
- 35:36Maybe Objective
- 41:09Java
- 41:43Javascript
- 42:06Summary
- 43:00Outro
