<https://developer.android.com/tools/agents/lightb...
# kotlin-toolchain
d
https://developer.android.com/tools/agents/lightbuild -- How many times you need to reinvent the wheel ? -- One more time please..
😆 5
😄 1
kodee floating 1
✅ 1
wait, is it based on Kotlin-toolchain / Amper ?
j
No, Lightbuild is not based on our product. It has been independently developed by Google, but it does have similarities in its config
😒 4
d
Well they promote it as "the build tool for AI Agents on Android" - there is a risk that it can become the mainstream way, you should invest in being AI friendly as well to keep up 🫠
I do not like when you split the ecosystem like that, Google owns Android, you own Kotlin and KMP, now you end up creating two distinct tools which will solve same pain points, instead to join forces and concentrate just on one good tool
Google said they will officially support KMP too
While Google has the freedom to start new projects and then shut them down, I don't think JetBrains has the same luxury. It should concentrate its resources on a few carefully chosen long-term initiatives, and competition from Google is risk for you
h
I don't think that’s a good take @Dumitru Preguza the kotlin-toolchain looks to be going for first class support for kmp while the light build is focused on Android. If you just care about Android you'd probably want to move towards the lightbuild but if you want kmp you can use the kotlin-toolchain. I wouldn't be surprised if one project leverages the other at some point. JetBrains integrating with this would be a trivial challenge compared to what they have done so far integrating with iOS and web targets
It's kind of the nature of software development to have competing standards and as the industry expands that's only going to become more so the case. That’s not a bad thing because you can pick what you like the most
d
I don't know, it's fragmentation of the ecosystem anyway
plus1 4
f
It looks like Lightbuild is just an abstraction over Gradle or other build tools so it's not that bad. But I would question how useful this is for "agentic development", because there is a lot of Gradle configs and error messages in the training data and basic Gradle usage is not that complicated.
âž• 1