Re:Porting 58000 lines of D and C++ to jai, Part 0: Why and How
by umanwizard on Wednesday November 23, 2022 @09:47PM
(#33727320)
Cargo isn’t part of Rust (the language) and you can use Rust without using Cargo.
Re:Porting 58000 lines of D and C++ to jai, Part 0: Why and How
by bsder on Thursday November 24, 2022 @12:38AM
(#33728088)
And yet cargo-raze still requires cargo and is still experimental after 5+ years of development effort by folks from Google.
It is my fondest hope that the Linux folks will finally beat the cargo out of Rust.
Re:Porting 58000 lines of D and C++ to jai, Part 0: Why and How
by umanwizard on Thursday November 24, 2022 @12:54AM
(#33728162)
> beat the cargo out of Rust
But cargo already isn’t in Rust. There are AFAIK no cargo-specific concepts that have leaked into Rust, the language. It is very straightforward to build Rust code without using cargo, for example with a makefile.
The reason other tools are slow to add support for rust is because cargo is so ubiquitous in the rust ecosystem that there is little point (I’d estimate that >99% of Rust code is built using Cargo), and not because of any technical impossibility.
Zig is getting an absolutely enormous boost from the fact that it is a self-contained C ecosystem that can cooperate with others. Zig has tripped into a very powerful niche--a lot of people LOATHE the build systems of the C/C++ world. If Zig gains very much more traction there, it's going to be extremely hard to dislodge.
I suspect that there are FAR more users of "Zig as C build system" than there are of "Zig as a language".