[stuhood]

> I’m more familiar with Bazel. Though I don’t “love it”, I spend plenty of time with it every day. Gazelle like rules for java would be nice.

We'd love your feedback on Pants' support for Java. Pants' "dependency inference" eliminates most BUILD file maintenance: https://blog.pantsbuild.org/automatically-unlocking-concurre...

[dfee]

Very interesting. I’m not sure if it’s actually the case, but I end up doing a ton of maintenance on BUILD files every day. I’ve become a sort of mini-master of designing target DAGs - in a way that’s upfront costly, but pays for itself over time with fast(er) rebuilds: I get very conservative with structure.

When deps are automatically gathered, do you tend to see that developers’ discipline becomes softened and code becomes highly interdependent again?

> In Guice, this would involve maintaining 23 BUILD files containing 622 individual java_library targets, each with many dependencies and exports listed. In larger monorepos, there’d be even more.

I’m all too familiar.