Hacker News Reader

> you might as well tell the user to just use cargo directly

For Rust projects, there really is no need for more than this. It might take a bit longer, but it’s simple and easy.

I really hope this trend doesn't continue, honestly. I shouldn't need the toolchain for a language that something was written in just to use that thing. It's very common with Go projects, too, but it's kind of a reversion back to the "./configure; make ; make install" days.

As far as I can tell, most of the package managers are just calling cargo under the covers anyway.

Only if they're building from scratch. Binary packages would have no need for cargo.

Most modern toolchains are robust, easy to use, and shared between many non-packages.

Go, Rust and Node.js cover a large portion of recent projects, and many others cheat with Docker or the like.

Reply on news.ycombinator.com