Have the end goals of Amper changed at all? Hone...

# amper

[eygraber]

Have the end goals of Amper changed at all?

Honestly (and with no disrespect intended for anyone working hard on Amper) I'm hoping it'll just quietly go away one day, solely because I think fracturing the build tool will end up hurting the community, and I believe Gradle is the better choice (and not just because I've invested so much in Gradle 😅).

[amakeev]

The end goal remains the same, which is to provide the best overall user experience for Kotlin and KMP platforms. We see a huge room for improvement in regard to the build tooling. With Amper we are exploring the ways to improve the situation

[eygraber]

Does "exploring the ways to improve the situation" mean getting learnings from Amper and integrating them back into KGP? Or is that not something that is decided yet?

[amakeev]

We do have continuous work on improving KGP as well. Still, with Amper we are trying a different approach, with less constraints, focused on simplicity, out-of the-box experience, and IDE support. Certain things and design decision might find their way into KGP as well, but no specific decision at this point. This will also depend on the feedback we are receiving, so please share your thought, what you would like to see in KGP

[eygraber]

I've been in a pretty good place with KGP lately 😄

Other than https://kotlinlang.slack.com/archives/CQ3GFJTU1/p1716401033553009 but I'm not sure if that's a KGP thing, or a language thing.

[christophsturm]

“invested so much in gradle” sounds to me like stockholm syndrome. 🙂 its just a build tool it should be easy, not something to invest in.

[eygraber]

I mean I've been using it for over 10 years, I spent time learning it, I've built tools around it, and I spend a lot of time tinkering with it because I find it to be fun to work with.

It wasn't always easy, but once I changed my approach to embracing it instead of fighting it everything changed. Also each new release brings a lot of improvements.