Bazel

“The rust support has gotten really good, and the maintainer for the rust rules works at OpenAI”

“This was incredibly easy to test in a Bazel monorepo due to the ability to inject patch files into 3rd party dependencies”

“Bazel like build system which can cache test executions so others don't need to rerun them”

“Bazel is an amazing build tool, but on the testing side it doesn't offer anything that special.”

“enables the ecosystem to scale way beyond what alternative BuildKit-based solutions can”

“since all the major AI labs are using Bazel, we know that the tools can support”

“That's nothing to scoff at, but not the headline numbers you see after a full hot build.”

“I've never personally experienced builds to be so slow to begin investigating bazel as an option for JS/TS”

“The setup cost for bazel just went down by a lot, and I don't think the industry as a whole is aware of that yet.”

“Bazel will get you build times ~10s with a warm cache for even massive projects.”

“With input addressing and hermetic builds, Nix and Bazel are systems that don't make you make that choice.”

“gets adopted by companies with developer support teams but feels frustrating for us ordinary folk”

“although I heard everyone say they worked so much better inside Google than outside it, had issues”

“Why not just embrace Content Based Addressing and the Bazel action cache?”

“this stuff feels like it's gotten soooo much better in the years since I've used Bazel”

“If you're not running an elite `bazel` or `buck2` RBE with `nativelink`? You're not even playing.”

“I've personally driven adoption of Bazel across two teams in our company over the last two years”

“I'm comfortable with its well-designed surface but whenever I've tried to understand the inner machinery I've given up”

“Done right, not only are your test results cached, but CI's test results can be cached too.”

“I would recommend learning the various "bazel query" variants starting with a plain "bazel query"”

“You want bazel. Once you've internalized the bazel (blaze) system, you want all builds and tests to work that way.”

“When I encounter macros written by someone else, they are awful, a mistake and the bane of my existence.”

“Since all dependencies are explicit you can pretty easily do a bazel (r)deps query”

“Google internally love to stick Bazel on everything and that's quite different (and overly complicated)”

“At some point I decided the complexity and overhead of building on top of bazel was more trouble than it was worth”

“Bazel, the default pick for very large codebases, also has support for C++20 modules.”

“a very standard build system used at many large tech companies. It splits fetches from build/test actions and allows blocking network for build/test actions with a single CLI flag.”

“Doesn't matter that the documentation sucks and it's unbelievable bloat for smaller companies”

“starting with Bazel/Buck/whatever your poison of choice is almost always a good move”

“Bazel will absolutely build stuff fully offline if you add the one step of running bazel sync //... in between cloning the repo and yanking the cable”

“Is the reason that it works for big tech that those can spare dozens of engineers to make it work?”

“It looks like their Bazel infrastructure optimized it by moving caching down to the file level.”

“these tools have a steep learning curve and require deep knowledge in more than one aspect”

“a lot of them involve either not getting full buy in from the developer team or not investing in building out Bazel correctly”

“you can make your life a lot easier by just making the whole repo a single Go module”

“That worked really well, with the only real limiting factor being the ultimate upper limit of a repo in Github”

“I think in an ideal world I just want Bazel or Nixos without the baggage that comes with them”

“Bazel is a largely language agnostic build system, with amazing build farm support.”

“The documentation had so many holes and what was there was either out of date or wildly inaccurate.”

“it's among the very few options that try to solve the hard problems of build systems”