Gradle Is Javamaxxing
blog.gradle.org
Gradle Is Javamaxxing
1–10 of 24 posts
Re: Gradle Is Javamaxxing
#2Offense is the best defense? Gradle is usually lagging behind, being unable to build projects with the latest JDK a week after it was released because of some asm bytecode dependency bullshit.
I have an unreasonable hatred of gradle and its imperative, choose-your-own-language build files, every buildfile being structured differently.
Hateful.
Not even talking about how slow it is, no I don't want the garbage demon running somewhere.
Re: Gradle Is Javamaxxing
#3Offense is the best defense? Gradle is usually lagging behind, being unable to build projects with the latest JDK a week after it was released because of some asm bytecode dependency bullshit. I have an unreasonable hatred of gradle and its imperative, choose-your-own-language build files, every buildfile being structured differently. Hateful. Not even talking about how slow it is, no I don't want the garbage demon r…
There is only one reason to use Gradle, the poor souls that have to put up with Android development requirements, and have fun with updating their projects, every single time there are DSL changes.
Re: Gradle Is Javamaxxing
#4Offense is the best defense? Gradle is usually lagging behind, being unable to build projects with the latest JDK a week after it was released because of some asm bytecode dependency bullshit. I have an unreasonable hatred of gradle and its imperative, choose-your-own-language build files, every buildfile being structured differently. Hateful. Not even talking about how slow it is, no I don't want the garbage demon r…
There is only one reason to use Gradle, the poor souls that have to put up with Android development requirements, and have fun with updating their projects, every single time there are DSL changes.
As someone who uses gradle largely out of inertia, I'm curious what you would pick as a better alternative.
Re: Gradle Is Javamaxxing
#5Earlier quoted context omitted.
There is only one reason to use Gradle, the poor souls that have to put up with Android development requirements, and have fun with updating their projects, every single time there are DSL changes.
As someone who uses gradle largely out of inertia, I'm curious what you would pick as a better alternative.
Maven as always.
I don't suffer from XML allergy, and Gradle is Ant all over again.
Worse, because it relies on a slow scripting language, or having to go through Kotlin, plus a background deamon.
Re: Gradle Is Javamaxxing
#6Earlier quoted context omitted.
As someone who uses gradle largely out of inertia, I'm curious what you would pick as a better alternative.
Maven as always. I don't suffer from XML allergy, and Gradle is Ant all over again. Worse, because it relies on a slow scripting language, or having to go through Kotlin, plus a background deamon.
Yeah I have long felt that if we think we need gradle, we should consider doing less crazy stuff in our build. Maven is plenty and any time I get back to a repo that has that instead of gradle or sbt I’m much happier.
Re: Gradle Is Javamaxxing
#7Earlier quoted context omitted.
As someone who uses gradle largely out of inertia, I'm curious what you would pick as a better alternative.
Maven as always. I don't suffer from XML allergy, and Gradle is Ant all over again. Worse, because it relies on a slow scripting language, or having to go through Kotlin, plus a background deamon.
I'm by-and-large fine with XML, having used it for many a year; however I really like working with XML when I can use Guile's SXML layer. For Maven it's not that important because POMs are simple enough, but for more complex things it's nice having a useful tool.
I actually don't mind Ant very much, but I haven't had good luck using Ivy for dependency management. Maven's been very nice in the decade and a half I've used it, Gradle's always felt off to me. I think there was also another Java build tool written in like Ruby or something, but I'm blanking on the name at the moment.
Re: Gradle Is Javamaxxing
#8Earlier quoted context omitted.
Maven as always. I don't suffer from XML allergy, and Gradle is Ant all over again. Worse, because it relies on a slow scripting language, or having to go through Kotlin, plus a background deamon.
Yeah I have long felt that if we think we need gradle, we should consider doing less crazy stuff in our build. Maven is plenty and any time I get back to a repo that has that instead of gradle or sbt I’m much happier.
Sbt is by far the worst. It’s the bane of my existence.
Re: Gradle Is Javamaxxing
#9Earlier quoted context omitted.
As someone who uses gradle largely out of inertia, I'm curious what you would pick as a better alternative.
Maven as always. I don't suffer from XML allergy, and Gradle is Ant all over again. Worse, because it relies on a slow scripting language, or having to go through Kotlin, plus a background deamon.
And for those that are allergic Maven 4 will offer alternative file types via extensions!
Re: Gradle Is Javamaxxing
#10Earlier quoted context omitted.
As someone who uses gradle largely out of inertia, I'm curious what you would pick as a better alternative.
Maven as always. I don't suffer from XML allergy, and Gradle is Ant all over again. Worse, because it relies on a slow scripting language, or having to go through Kotlin, plus a background deamon.
I always hated Maven, until I started using Gradle.