Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

The only reason to ever touch it, are Android projects. I try to stay Gradle clean as much as possible.


Same. The Gradle setup it was making was insanely complicated, then the Gradle-free script I forced it to make was very simple. There's no way I would've used Gradle without the LLM either.


Kotlin projects too.


All our products and tools around them are built by using Gradle, for more than a decade now. We have no Android and no Kotlin-only projects. I would never switch it for Maven. In fact, I don't remember the last time I used Maven for a Java project. But I guess everyone has their preference.


I prefer Maven. It’s simpler or maybe I just know it. But with Kotlin I’ll still choose gradle because that’s the Kotlin ecosystem.


Nah, Maven also does the job, and I don't do Kotlin anyway.


Maven does not properly do the job for kotlin projects. The Kotlin ecosystem and all of its plugins are very much gradle focused. You have to do bizarre things in maven to get them to behave properly.


Yet another reason not to bother then, it used to work a few years ago.


Plenty of reasons. The Java team can’t ship basic language features that will improve the day to day lives of most people.




Consider applying for YC's Winter 2027 batch! Applications are open till November 2.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: