Just discovered <https://github.com/gradle/declara...

# gradle

[Edoardo Luppi]

Just discovered https://github.com/gradle/declarative-gradle
How does it compare to Amper?

[Vampire]

Probably better as that in the #declarative-gradle channel of the Gradle Slack

[Vampire]

But generally probably different approaches to reach the same goal

[Vampire]

Besides the obvious YAML vs. Kotlin Subset of course

[Edoardo Luppi]

Yeah seems like they want to accomplish the same thing. I wonder if Amper could have been built over this Gradle alternative.

[CLOVIS]

> Yeah seems like they want to accomplish the same thing. I wonder if Amper could have been built over this Gradle alternative.
Considering Declarative Gradle and Amper were announced basically at the same time, I suspect they were originally intended to be a single thing but split into different projects for some reason

[Vampire]

I'd assume they were simply parallel developed approaches

[Edoardo Luppi]

What I don't like is the excessive fragmentation of build approaches.

[wolf]

There is some discussion about the Gradle/Google/Jetbrains collaboration and Amper in the declarative Gradle blog post

[stantronic]

I'd rather not have to migrate from Gradle. Especially as Gradle has been so embracing of Kotlin

[Vampire]

You don't have to.
Both approaches are on-top-of Gradle.
And both are - and hopefully stay - optional layers.

[Vampire]

While well, maybe it would even be a good thing to enforce declarative Gradle in build scripts,
to enforce having imperative logic in convention plugins. 🙂