Why are JVM build tools so awful?
gradle.png
md5: 9db9b52a... 🔍
ITT we discuss JVM build tools.
IMO Gradle is the worst part of Android development, although Google deprecating perfectly fine libraries so product managers can get promoted is a close second.
>Your version of the Android Gradle Plugin is incompatible with (whatever, ignore)
>You are using features that will be deprecated in Gradle 9.0
>Oops, you need to sync. That'll be 5 minutes of your life
>I hope you told your manager you need a week to upgrade Gradle
>Surely we'll get the API right in MAJOR VERSION 9
>Three Gradle dialects (Groovy, Kotlin, Declarative Kotlin)
>Three ways to do something. Two deprecated, one "recommended" but missing key features
>Documentation is obtuse, abstract bullshit devoid of usefulness
>Gradle forums are full of smug, verbose "you're holding it wrong" Europeans (same people who write the docs)
>You want to open an Android project from over a year ago? Hah, fuck you
uv, go tools, MSBuild/the dotnet CLI, and cargo are all faster than Gradle and require significantly less bullshit. I would pick anything other than the JVM for a new project solely because of Gradle, which is unfortunate because I actually like Kotlin and Java. In fact, they invented the entire concept of Android modularization to cover up Gradle's slowness. Most apps don't need it and the K2 compiler supports incremental builds.
>skill issue
Sorry, I don't have the luxury of a build team with make-work jobs provided by Gradle, Inc.
https://github.com/JetBrains/amper
I hope Amper becomes the standard so I never have to deal with another major version migration because Gradle, Inc. wanted to sell more enterprise support contracts. What a rapacious waste of time and electricity. Amper alpha will probably be more stable than Gradle's 10th iteration. Thousands of tons of carbon dioxide will be saved. It is truly insane that such an abomination as Gradle exists in the same world as vidya with real-time 4K graphics, ray tracing, and physics all in 17ms or less.
IMO Gradle is the worst part of Android development, although Google deprecating perfectly fine libraries so product managers can get promoted is a close second.
>Your version of the Android Gradle Plugin is incompatible with (whatever, ignore)
>You are using features that will be deprecated in Gradle 9.0
>Oops, you need to sync. That'll be 5 minutes of your life
>I hope you told your manager you need a week to upgrade Gradle
>Surely we'll get the API right in MAJOR VERSION 9
>Three Gradle dialects (Groovy, Kotlin, Declarative Kotlin)
>Three ways to do something. Two deprecated, one "recommended" but missing key features
>Documentation is obtuse, abstract bullshit devoid of usefulness
>Gradle forums are full of smug, verbose "you're holding it wrong" Europeans (same people who write the docs)
>You want to open an Android project from over a year ago? Hah, fuck you
uv, go tools, MSBuild/the dotnet CLI, and cargo are all faster than Gradle and require significantly less bullshit. I would pick anything other than the JVM for a new project solely because of Gradle, which is unfortunate because I actually like Kotlin and Java. In fact, they invented the entire concept of Android modularization to cover up Gradle's slowness. Most apps don't need it and the K2 compiler supports incremental builds.
>skill issue
Sorry, I don't have the luxury of a build team with make-work jobs provided by Gradle, Inc.
https://github.com/JetBrains/amper
I hope Amper becomes the standard so I never have to deal with another major version migration because Gradle, Inc. wanted to sell more enterprise support contracts. What a rapacious waste of time and electricity. Amper alpha will probably be more stable than Gradle's 10th iteration. Thousands of tons of carbon dioxide will be saved. It is truly insane that such an abomination as Gradle exists in the same world as vidya with real-time 4K graphics, ray tracing, and physics all in 17ms or less.
