It trumps all other concerns. Because if Rust weren’t easy to get started with, we wouldn’t be having this conversation in the first place. Language ecosystems from small players have to optimize for ease of use, otherwise they die. Google can afford to do otherwise.
-
This Tweet is unavailable.
-
-
This Tweet is unavailable.
-
I don’t recall ease-of-use as part of the pitch to me either, I have to say. It’s great, but only once it’s off the ground enough that people _want_ to use it. EOU promotes adoption, and you don’t want a lot of 0.1 adoption anyway IMO.
1 reply 0 retweets 1 like -
This whole conversation is driving me crazy because we’re starting from the position “Bazel good, Cargo bad” without even stopping to understand what the specific problems that Rust is currently facing are. So far I’ve heard talk about caching LLVM, but that is a Travis issue.
2 replies 0 retweets 1 like -
This Tweet is unavailable.
-
Again, for the millionth time, that is a CI problem, not a build system problem.
2 replies 0 retweets 0 likes -
Why is it hard (or even non-pathologically possible) for the CI system to do the right thing here? CI is choked because builds take a long time, typically.
1 reply 0 retweets 0 likes -
It is very much not the case that changing a .md file in the docs causes an LLVM rebuild. This has *NEVER* been the case in Rust’s 10 year history.
1 reply 0 retweets 1 like -
Nor is it the case that changing a .rs file in the compiler causes an LLVM rebuild. Again, this has *never* been the case.
1 reply 0 retweets 1 like
So if LLVM is being rebuilt when the docs change, it is a problem specific to the CI, and it should be solved *there*. Because if you change the build system to Bazel, and don’t fix *that* issue, it will *still* be a problem.
-
-
This Tweet is unavailable.
-
Now we’re getting somewhere. The reason why that triggered a rebuild is that the compiler couldn’t tell—or, more likely, incremental compilation lacked the hooks to tell the build system—that a rebuild was not necessary.
1 reply 0 retweets 0 likes - 13 more replies
-
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.