4 ms·
Bazel ergonomics / DX sucks but it does deliver on correct and fast.
by pharmakom 4y ago
Bazel ergonomics / DX sucks but it does deliver on correct and fast.
- tantalor 4y agoCompared to what? Do you mean writing build rules, or the behind-the-scenes stuff?
- asadawadia 4y agoeverything
- marcyb5st 4y agoI agree on adding non native build rules, but once you get that over it is pretty epic. 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).
- sp33der89 4y agoSBT is a lot less scary these days IMHO.
- vips7L 4y agoSBT is the bane of my existence.
- rtpg 4y agoFor a lot of people the alternatives are things like fabric/invoke. 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”
- radvani13 4y agoHi, pharmakom I am the PM at bazel and would love to learn more about your DX pain points. Looking forward to connecting Regards, Radhika
- pharmakom 4y agoSure! 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.