You'll get wildly different answers depending on who you ask. Most ex-Googlers appreciate Bazel. Folks used to ergonomic single-language builds dislike it. In

You'll get wildly different answers depending on who you ask. Most ex-Googlers appreciate Bazel. Folks used to ergonomic single-language builds dislike it. In my experience, Bazel works best when: - You have a monorepo. - You have one engineer who knows it in and out and can stay current. - You use several languages well-supported by Bazel (Protobuf, Go, Java, Kotlin). The benefits are a single way to build and run all tests and binaries across all languages. Bazel CI providers (BuildBuddy, EngFlow) are much nicer than YAML engineering in other CI systems. I have an old comment that's still representative of my experience: https://news.ycombinator.com/item?id=32831555 https://news.ycombinator.com/item?id=32831555