[doctorpangloss]

Another point of view is, don't use Bazel. In my experience, Gradle is less of a headache and well supported.

[metadat]

Gradle is an anti-pattern. Just stick with Maven and live a happy life.

As someone who's used Gradle tons, 6 months ago I wrote in detail about why not gradle:

https://news.ycombinator.com/item?id=38875936

Gradle still might less bad than Bazel, though.

[EdwardDiego]

I'm firmly in the Maven is better than Gradle camp. Yes, it's less flexible, that's why I like it.

Gradle might be better if it wasn't a poorly documented Groovy/Kotlin DSL where everything is a closure, but I do like the fact that if you want to do something in Maven you need a plugin that couples to known points in the lifecycle. It makes it explicit what is doing what and where.

And fully agree on the incredible pain of Gradle upgrades.

[shepherdjerred]

Maven is one of my favorite package managers. It's not as fancy as npm, cargo, go, etc., but it works consistently well and I never have to fight it.

[jscheel]

For python? Gradle doesn't really support python.

[kaba0]

I mean, gradle is a generic build tool. It could support it, just as it can be used to compile C (I have done the latter).