Our pain point is “change one line in the script crate, observe the long cycle time”. Bazel would not help us with that. Compiler improvements would.
Let’s back up. (1) We have to have a package manager. (2) We have to have simple Cargo.toml files (i.e. convention over configuration). (3) We have to make it easy to install Rust and Cargo. (4) We have to make Cargo work with many build systems; e.g. Firefox’s.
-
-
This Tweet is unavailable.
-
I don’t love http://build.rs files either!
End of conversation
-
-
-
(1) Bazel is not a package manager. (2) CoC requires that we have Rust-specific knowledge in the build system. That’s been most of the work in Cargo. Job scheduling is relatively easy. (3) Bazel required JVM at the time and adds to download size. (4) Cargo is minimal, which helps
-
This Tweet is unavailable.
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.