riff
Riff automatically provides external dependencies for Rust projects, with support for other languages coming soon. (by DeterminateSystems)
riff
Riff automatically provides external dependencies for Rust projects, with support for other languages coming soon. (by DeterminateSystems)
riff | riff | |
---|---|---|
8 | 8 | |
487 | 487 | |
- | - | |
10.0 | 10.0 | |
7 months ago | 7 months ago | |
Rust | Rust | |
Mozilla Public License 2.0 | Mozilla Public License 2.0 |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
riff
Posts with mentions or reviews of riff.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-01-28.
-
nix-init - Generate Nix packages from URLs with hash prefetching, dependency inference, license detection, and more
Dependency inference for Rust packages using the Riff registry and python projects
-
Generate Nix packages from URLs with hash prefetching and dependency inference
- Dependency inference for Rust packages using the [Riff](https://github.com/DeterminateSystems/riff) registry and python projects
-
An example providing rust toolchain for Linux/macOS using devenv.sh
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.
-
devenv: Fast, Declarative, Reproducible, and Composable Developer Environments
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.
-
An invitation to Rust maintainers from Determinate Systems
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.
-
Introducing Riff, a Nix-based tool for automatically providing external dependencies to Rust projects
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.
riff
Posts with mentions or reviews of riff.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-01-28.
-
nix-init - Generate Nix packages from URLs with hash prefetching, dependency inference, license detection, and more
Dependency inference for Rust packages using the Riff registry and python projects
-
Generate Nix packages from URLs with hash prefetching and dependency inference
- Dependency inference for Rust packages using the [Riff](https://github.com/DeterminateSystems/riff) registry and python projects
-
An example providing rust toolchain for Linux/macOS using devenv.sh
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.
-
devenv: Fast, Declarative, Reproducible, and Composable Developer Environments
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.
-
An invitation to Rust maintainers from Determinate Systems
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.
-
Introducing Riff, a Nix-based tool for automatically providing external dependencies to Rust projects
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.
What are some alternatives?
When comparing riff and riff you can also consider the following projects:
rust-overlay - Pure and reproducible nix overlay of binary distributed rust toolchains
difftastic - a structural diff that understands syntax 🟥🟩
nixpkgs-pytools - Tools for removing the tedious nature of creating nixpkgs derivations [maintainer=@costrouc]
devbox - Instant, easy, and predictable development environments
devenv - Pluggable development environments builder that has potential to support any language or framework environment
riff - A diff filter highlighting which line parts have changed