gradle has become the JUnit 3 of the 2010s. Impossible to avoid but annoying to use
09/28/2017, 8:13 AM
i disagree on the impossible to avoid
but i agree that’s it’s mandatory on android 😧
btw, “annoying” is an english understatement
09/28/2017, 2:21 PM
@nfrankel I want to be fair, hence "annoying". Gradle has unleashed a lot of flexibility and power and I want to acknowledge that. It's just still pretty rough around the edges because of its old age and its Groovy roots, and it makes me sad we have to live with that. But the situation is certainly not as dire as when we were stuck with JUnit 3, which was truly horrible and inadequate for the job even back then.
09/28/2017, 2:26 PM
Gradle is flawed from the start
because it provides “flexibility”
i don’t want my build tool to be flexible
i want it to be stable and opinionated - just like Maven
when you want to change something in Maven
you need to create a plugin, it’s painful
hence, you probably think twice before creating one
and fall back to the Maven way
in Gradle, you cannot do whatever you want
you code your build (but don’t test it - who creates code that is not tested?)
and whoever wants to do anything differently
for no other reason than to do it “his” way
he can just code it...
i’ve experienced it, it’s a nightmare
09/28/2017, 2:43 PM
That's where I disagree; being able to write code directly in the build file whenever it's necessary is a productivity booster. Already back in the ant days, I wanted to do things like simple expressions or even basic inheritance (I want to run this task with all the default settings except this particular setting that I want to override").
And I create code that's not tested all the time, as does most of the industry I bet. It works just fine.
09/28/2017, 3:04 PM
as you told, that’s where we disagree
between working alone and working in teams 🙂