nurl VS riff

you can use nurl to get the hash of fetchers, which uses nix flake prefetch github:/ for github urls under the hood, you can use that too if you don't mind typing a little more

All other fetchers supported by nurl are also supported, you just have to specify the tags manually

added, thanks for the suggestion

Dependency inference for Rust packages using the Riff registry and python projects

- Dependency inference for Rust packages using the [Riff](https://github.com/DeterminateSystems/riff) registry and python projects

In this language context specifically, if one wanted to manage their workspace with Nix I would reach for Riff and/or oxalica/rust-overlay first, since they are deliberately more aware of Rust-specific nuance. In the latter's case it has compatibility paths with rustup-toolchain files as well, for allowing your peers who can't or won't adopt Nix to continue to feel like first-class participants in the project. Another alternative I don't have experience with would be nix-community/fenix.

Seems to have spiritual overlap with what I understand the goals of Riff to be. Both projects are early stage and not able to cover every language ecosystem yet.

No, I wouldn't say that's obvious. Riff doesn't need 100% buy-in from all Rust maintainers because not all Rust projects have external dependencies. But what we've found in our research on the crate ecosystem is that there are particularly busy "nodes" in the dependency graph. Each time a busy "node" with external dependencies adds a few lines to Cargo.toml, that un-breaks a number of downstream project builds. Our internal registry is pretty small but even that has substantially increased the % of projects in which riff run cargo build works without issue. It's an asymptotic approach and we're confident that sufficient awareness could get us pretty darned close.

We currently have a hard-coded [registry](https://github.com/DeterminateSystems/riff/blob/main/registry/registry.json) of some known per-crate dependencies. But the goal is less to hard-code ever more dependencies and more to convince maintainers to explicitly [declare dependencies](https://github.com/determinateSystems/riff#how-to-declare-package-inputs) in their `Cargo.toml` under `package.metadata.riff`. Because Riff uses `cargo metadata` for the entirety of the crate dependency graph, explicit dependency declarations actually benefit downstream crates as well.