← Back to context

Comment by kerkeslager

10 months ago

> 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.

> > 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.

and

> My goal is to be able to build my project with as little effort as possible. "Effort" includes evaluating different tools and reading their documentation.

Apparently, I don't know that, or I'm being trolled. What even is knowing something when folks contradict themselves two replies in?

> If you've not used them, then your confidence that they are equivalent to Cargo comes from where?

The endorsements of others who have used the tools. But, I'm starting to suspect that you wouldn't consider any endorsement of any tool other than cargo as valid...

> 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.

Note that I said "build tool". A package management system is a hair more complicated. You'll need a week instead of an afternoon.

  • > What even is knowing something when folks contradict themselves two replies in?

    You quoted two bits and are claiming they are contradictory, but they aren't.

    I said, "My goal is to be able to build my project with as little effort as possible. "Effort" includes evaluating different tools and reading their documentation."

    That's not "I don't want to read about any other build systems besides Cargo."

    I'm happy to read about other build systems. I would be extremely happy if I found one as easy as Cargo for C, but I'm quite confident that doesn't exist.

    But it took me all of 3 minutes to learn how to do everything I need to do with Cargo, and it was simple enough that I have it committed to memory and never have to read it again. I don't want waste time reading about build systems that are immediately obviously harder to use and don't do anything more, because that is a complete and utter waste of time.

    And I say "You know that" because it's not some puzzle if you were looking to understand what I say instead of attack it.

    > Note that I said "build tool". A package management system is a hair more complicated. You'll need a week instead of an afternoon.

    Your confidence in me is charming.