Depends. Is stuff like context receivers (https://nomisrev.github.io/context-receivers/ https://nomisrev.github.io/context-receivers/) needed ? No, although it'

Depends. Is stuff like context receivers (https://nomisrev.github.io/context-receivers/ https://nomisrev.github.io/context-receivers/) needed ? No, although it's a fun experiment. Are multiple receivers needed (https://youtrack.jetbrains.com/issue/KT-10468/Multiple-receivers-on-extension-functionsproperties https://youtrack.jetbrains.com/issue/KT-10468/Multiple-recei...) ? Not really, but when you are dealing with the JVM, nested class hell is a very common thing, and cleaning up your code is always pleasant. Implicit namespacing ? (https://youtrack.jetbrains.com/issue/KT-11968/Research-and-prototype-namespace-based-solution-for-statics-and-static-extensions https://youtrack.jetbrains.com/issue/KT-11968/Research-and-p...) Fun thing to get. The thing is, they're all optional. You're never going to use any of these features if you don't need them. Your code can stay as a nested list of calls. But put them all together, and you can have code that is super explicit about what it needs to do, without having to re-pass things that are already there.