[jinwoo68]

To be fair, Bazel didn't exist when Chrome started.

[dijit]

Even so, a build system migration of any kind being anything other than Bazel given the design goals of Bazel and the heritage of Chrome is an implicit indictment of Bazel itself.

I say this as a fan of Bazel.

[7e]

Most likely Chromium needs to build on a system which doesn’t support Java. Like ChromeOS. That excludes Bazel, at least unless cross-compilation is supported (likely a monstrous headache for ChromeOS). It’s a good reason to rewrite Bazel in Rust.

[arccy]

moving to bazel might be a lot more work vs a drop in replacement which is what siso looks like atm.

[jefftk]

Bazel didn't even exist when they moved from gyp to ninja.

[westurner]

Blaze (and gtest) did exist then, but it was integrated with Omega scheduler.

[jinwoo68]

IIRC even blaze didn't exist. The Chrome project existed before I joined Google (in 2007) but blaze came out after I joined Google.