Again, strongly disagree. Bazel focuses on the big company workflow. Cargo focuses on the open source workflow. It would have been a mistake to try to serve big companies first without focusing on package management/code sharing.
-
This Tweet is unavailable.
-
-
This Tweet is unavailable.
-
Replying to @sayrer @graydon_pub and
I’m not talking about big companies vs. small companies. I’m talking about companies vs. the open source ecosystem. How many large open source projects use Bazel? Not even Chromium does!
1 reply 0 retweets 0 likes -
(And one of the reasons why Bazel is not used by Chromium is a lack of emphasis on Windows support, which again goes back to the open source ecosystem vs. companies.)
1 reply 0 retweets 0 likes -
This Tweet is unavailable.
-
Replying to @sayrer @graydon_pub and
Explain how Cargo does not have reproducible builds. Look, if Rust had said “we’re not going to provide a package manager, just use Bazel” the language probably would have died.
1 reply 0 retweets 4 likes -
This Tweet is unavailable.
-
Replying to @sayrer @graydon_pub and
“Multiple languages in one organization” is simply not as important of a problem to solve as “bootstrap a Rust ecosystem so that the libraries people need are available”. Because if we didn’t solve the latter, then companies wouldn’t have considered Rust viable to begin with.
2 replies 0 retweets 1 like -
This Tweet is unavailable.
Evidence for what assertion?
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.