3 ms·
> Maybe you have some really complicated use case that makes cargo insufficient, but really, it's pretty damn nice and it's integrated with everything. I feel
by insanitybit 4y ago
> Maybe you have some really complicated use case that makes cargo insufficient, but really, it's pretty damn nice and it's integrated with everything.
I feel like our use case at Grapl wasn't particularly crazy. It was just slightly more than "I'm a dev building a library and publishing it" - we had a workspace with multiple devs and CI/CD. CI/CD was really slow - issues with caching, rerunning unnecessary tests, etc.
Plus we had some Python code so unifying our builds would have been ncie.
- swsieber 4y agoThis. As soon as you have to integrate multiple languages, jumping from the native build tool to an integrated build tool is a must. Why? So that you can saturate all your threads in an efficient way.
- twunde 4y agoHey Colin :wave: (I hope you're bringing Rust to DD) To add onto this, Grapl had a moderate sized codebase with less than 10 engineers. I do think we could have done some optimizations in cargo, but it's simply much easier to use a tool like Bazel/pants etc that does the work for you as long as it supports your language of choice.
- insanitybit 4y ago:D Hey