Bazel ergonomics / DX sucks but it does deliver on correct and fast.
Do you mean writing build rules, or the behind-the-scenes stuff?
Also, I don't think it's more complex than SBT/Gradle (what I was using before, but admittedly was a long time ago so I don't know now).
If you don’t care about correctness there a loads of options that work well, and don’t have problems supporting esoteric use cases such as …“let a command generate a folder of data”
I am the PM at bazel and would love to learn more about your DX pain points. Looking forward to connecting
Regards, Radhika
I have a few annoyances with Bazel, but the biggest is quite fundamental. I really dislike how all rules share the same namespace for outputs. You can’t define two rules that output to the same path, and there is really little reason for this. Buck does not have this issue.