
Features Left Out: Pattern Matching and Ternary

The programming language after Kotlin – with the creator of Kotlin
Topic 4 of 12
Published Feb 12, 2026 · Clip 40:43–44:54 (4:11)
Andrew discusses features Kotlin considered but deliberately excluded. Pattern matching, inspired by Scala and Haskell, was postponed when he realized while writing the parser that it was 'an entire language in size'; smart casts plus destructuring give 80% of the benefit. He then tells the 'saddest story' of Kotlin design: omitting the ternary operator because Kotlin's if is an expression, a decision he now considers a mistake since it cannot be retrofitted into the current syntax.