Because the few projects that I've seen using it assume an infinite amount of RAM and CPU threads to be able to compile. On top of that their version of 'make' doesn't recognize or honor MAKEOPTS. Instead you have to create a world readable file off the root of the filesystem to control it's behavior.
You're not compelled to use cargo to make Rust projects. If you love Make so much, write a rule to turn.rs to.o and invoke rustc with it. That might even be what someone does if they were linking C and Rust into the same binary.
Personally I like the fact that cargo lets me pull, build and link an external dependency with a single line of text in most cases.
Possible reason (Score:1)
Because the few projects that I've seen using it assume an infinite amount of RAM and CPU threads to be able to compile. On top of that their version of 'make' doesn't recognize or honor MAKEOPTS. Instead you have to create a world readable file off the root of the filesystem to control it's behavior.
Re:Possible reason (Score:2)
Personally I like the fact that cargo lets me pull, build and link an external dependency with a single line of text in most cases.