A modern programming language that makes developers happier.

kotlinlang

<@U41021CCB> I took a peek now. Is `orElse` really "Kotlin"? It feels more like Java 8. `?:` usually is preferred in Kotlin, so I don't think we need those really. They are just more ways to say the same. While looking at this I got an other idea. Every Component already has a `config` object, so what if the `App` class also got one, and you could easily access the `config` object of other Components? Then you could use the `App` class's config object as a global config store, without needing a Context. Inside a Component, `config` would always point to the current config, and you could access other classes config object via something like `config&lt;MyApp&gt;` or something. I haven't thought this through yet, just got the idea while reading.