... Another plan to take over the universe for Kotlin is... We have ability with our data and processing of all public maven repos to resolve full build dependencies and even let you fix conflicts in old libraries with back in time shading. So we clean that up and replace the aether, ivy and other dependency with one that is fast, parallel downloads, can pin the dependencies list, identifies all potential problems and let's you resolve them with useful and easy adjustments. Add things like knowing API compatibility ahead of time, binary difference in classes (even shaded variations knowing they do the same), and attributes like Kotlin ABI, Scala compiler version, Java jdk compatibility. Multiple targets. And also library author added metadata like 'safe upgrade from 1.5.4' so auto upgrades can happen. And more. Gradle will do it slowly over a year and badly by following model started by adept but causing new problems and not finding or solving all the typical ones. So an open window for a Kotlin built tool. And it is a game changer that can attract a lot of attention. We have a roughed in version. And we're thinking about pushing 'brikk' before JavaOne. I can dedicate someone to Intellij plugin and that is the biggest remainig hurdle.