Comment by nanolith
10 months ago
If your goal is "I want to use Cargo and nothing else because that would require effort to learn to type a different command", then use Cargo.
But, there are similar build and package systems for C. Cargo is nothing special.
> If your goal is "I want to use Cargo and nothing else because that would require effort to learn to type a different command", then use Cargo.
That's not my goal, and you know that.
> But, there are similar build and package systems for C.
The reason you aren't naming one is that they obviously aren't similar in ways that matter.
> That's not my goal, and you know that.
Didn't you just say that you didn't want to read about any other build system, as that would involve effort? Uh... okay.
> The reason you aren't naming one is that they obviously _aren't_ similar in ways that matter.
Or, as I said previously, I'm not interested in endorsing build tools I haven't used, because I'm not in the market for a cargo clone. They exist. Plenty of folks I know are happy with one or another. Build tools are not difficult to write. As with the article, if you don't like existing build tools, spend an afternoon writing your own. It's a little graph theory and job management.
> Didn't you just say that you didn't want to read about any other build system, as that would involve effort?
No, I did not say that, and you also know that.
> Or, as I said previously, I'm not interested in endorsing build tools I haven't used, because I'm not in the market for a cargo clone. They exist.
If you've not used them, then your confidence that they are equivalent to Cargo comes from where?
> Build tools are not difficult to write. As with the article, if you don't like existing build tools, spend an afternoon writing your own. It's a little graph theory and job management.
I'm the author of the Fur programming language, which does need a package management system, so I will be doing this at some point. But I very much doubt that it will be as easy as you claim.
2 replies →