@sir "Attempts to integrate it with other build systems have been met with hostility from the Rust & Cargo teams." Any examples/citations of this?

@curls There's a few threads from Meson that were linked on HN at least: github.com/mesonbuild/meson/is github.com/mesonbuild/meson/pu (Cargo team members mostly show up on the PR)

@curls You're welcome. It's a hard problem. as someone who's dabbled a fair amount with Nix and packaging for Nixpkgs, the tradeoffs between integrated tools and experiences like Cargo and "larger" build systems like Meson or Bazel are difficult. you want the easy things for developers to be the right things, but that makes more effort for others. Cargo has been getting better about telling you what it wants to do, but you won't ever be free without a maintained reimplementation.

@curls cargo evolves to better serve developers over time along with a language that tries to move past poor design decisions (not removing them outright, but discouraging them in new code). Meson is based on a language where there's never been a really good build system, and it has less to chase and grow compatibility for. I don't see a generic solution in the future outside of a nix-like build system that combines sandboxed execution of whatever with bits of custom glue code.

@bb010g I am a bit fuzzy about the details, as I have no experience with rust, but it seems like cargo is missing features that besides hindering integration, just make it less robust in general. It makes me apprehensive to learn rust in the first place, knowing that realistically Cargo is the only build system I could ever use.

@curls Working with Cargo & Rust yourself will give you better answers, but if you want to ask about what you think Cargo may struggle with, i'll try to give you the best answers I can. (cargo's been really great in my experiences.)

Sign in to participate in the conversation

Chitter is a social network fostering a friendly, inclusive, and incredibly soft community.