<Amper – Improving the Build Tooling User Experien...
# feed
r
Amper – Improving the Build Tooling User Experience  Time and time again people adopting Kotlin have told us that they find dealing with build systems challenging. While many projects use wizards to configure environments so they’re ready for developers to get started, these also need to be maintained. New modules, platforms, dependencies, and other changes happen, which often leads to developers spending more […]
👀 4
🎉 5
👍 5
s
It barely works though.... (Dutch speaking folks'll understand this joke 😁🇳🇱)
f
Why yaml 😢 for configuration? Kotlin DSL is perfectly concise and provides type safety. Amper is just an opinionated gradle plugin, which could be configured directly in gradle.
Copy code
plugins { 
  alias(libs.plugins.amper)
}

amper {
  product = IOS_APP
  dependencies {
    add("../shared")
  }
  settings {
    compose = ENABLED
  }
}
I fear that we will end up with a mix of gradle + amper configurations which will actually be more complex and with a bigger learning curve that just one build system (gradle). 🤔
👆 7
👆🏾 1
c
I suppose their goal is to have it become standalone once it has enough features, and completely drop Gradle then?
☝️ 1
🤞 1
nono 2
m
@franztesca it explains this in the blog post