rfcs VS rfcs

Compare rfcs vs rfcs and see what are their differences.

rfcs

The Nix community RFCs (by tweag)

rfcs

The Nix community RFCs (by NixOS)
Our great sponsors
  • Scout APM - Truly a developer’s best friend
  • SonarLint - Clean code begins in your IDE with SonarLint
  • talent.io - Download talent.io’s Tech Salary Report
rfcs rfcs
2 24
16 315
- 4.4%
0.0 5.3
10 months ago 4 days ago
Creative Commons Attribution Share Alike 4.0 Creative Commons Attribution Share Alike 4.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.

rfcs

Posts with mentions or reviews of rfcs. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2022-09-11.
  • Is NixOS fundamentally a more secure OS?
    4 projects | reddit.com/r/NixOS | 11 Sep 2022
    https://www.tweag.io/blog/2020-09-10-nix-cas/ https://github.com/NixOS/rfcs/pull/62 https://github.com/NixOS/rfcs/pull/17 https://github.com/tweag/rfcs/blob/cas-rfc/rfcs/0062-content-addressed-paths.md https://github.com/wmertens/rfcs/blob/master/rfcs/0017-intensional-store.md https://discourse.nixos.org/t/content-addressed-nix-call-for-testers/12881
  • NixOS History and Our Experience - Nix, Null, Nada, Nothing
    8 projects | reddit.com/r/NixOS | 26 Jan 2022
    Content-addressable-storepath Derivations (CAS): Not something that users will mostly interact with directly, but one of the "pitfalls" of nix right now is that updates to "fundamental packages" like glibc, will cause most packages to be re-built. CAS derivation may help significantly in this regards, because there may be a point in which the changes don't have meaningful impact on a given down stream dependencies (for example, a pure python package); the CAS derivation may get to a point where it can start "re-using" existing builds after it determined that the contents exactly match. More info: https://github.com/tweag/rfcs/blob/cas-rfc/rfcs/0062-content-addressed-paths.md

rfcs

Posts with mentions or reviews of rfcs. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2022-09-11.
  • Is NixOS fundamentally a more secure OS?
    4 projects | reddit.com/r/NixOS | 11 Sep 2022
    https://www.tweag.io/blog/2020-09-10-nix-cas/ https://github.com/NixOS/rfcs/pull/62 https://github.com/NixOS/rfcs/pull/17 https://github.com/tweag/rfcs/blob/cas-rfc/rfcs/0062-content-addressed-paths.md https://github.com/wmertens/rfcs/blob/master/rfcs/0017-intensional-store.md https://discourse.nixos.org/t/content-addressed-nix-call-for-testers/12881
  • Nix and NixOS Get So Close to Perfect
    11 projects | news.ycombinator.com | 24 Apr 2022
    a) buildGoModule is a higher-level function that will return the result of mkDerivation in a way that reuses everything that is common to Go modules. So it makes perfect sense from the perspective of a maintainer who wants to reduce the size of nixpkgs as much as possible, which is already one of the largest Git repositories on GitHub.

    b) Nixpkgs library functions like buildGoModule, with the need to maintain the separate vendor hash, come from a desire to write pure Nix functions without network access, i.e. there is no need to re-download the vendored dependencies if they already exist in the local Nix store cache. Indeed, the fact that there is only a single vendor hash represents a pragmatic compromise; whenever any dependency changes, the entire vendored dependency tree needs to be re-downloaded and rebuilt; if the hashes of the individual dependencies were tracked, then Nix would understand to only download the dependencies which had changed. The reason why Nix can't compute the dependency hashes of each dependency internally, and only then try to check the Nix store and see if they exist there, is because Nix does not yet support recursive calls: https://github.com/NixOS/nix/issues/13 (nearly ten years old). However, the RFC for adding support was finally merged: https://github.com/NixOS/rfcs/pull/92 and so support will come soon enough.

    So basically:

  • Chrome technically unusable on NixOS
    7 projects | reddit.com/r/NixOS | 15 Apr 2022
    Why not write an RFC instead of hurling insults, and calling for maintainers, who don't even get paid, to be fired?
  • Ask HN: Who operates at scale without containers?
    7 projects | news.ycombinator.com | 22 Mar 2022
    Please check out https://github.com/NixOS/rfcs/pull/109 !

    I absolutely agree language-specific package managers need better support. Nix RFC 109 is a simple-stupid way to get some "important from derivation" in Nixpkgs, so we can collectively dogfood them "lang2nix" tools and finally make them good.

    It is really sad to me that many users understandly think "hmm, C is crazy, surely this Nix should be even better with more uniform language ecosystems packages!", only to die on the hell of the lang2nixs all being just not quite good enough. This is huge stumbling block for developement shops that try to use Nix that I want to see removed!

  • Nix: An idea whose time has come
    17 projects | news.ycombinator.com | 18 Feb 2022
    I am not so sure about that. Nixpkgs is a big ball because it is the final integration point. And I do in fact find myself refactoring individual packages and the infra at the same time.

    https://github.com/NixOS/rfcs/pull/109/ I wrote to hopefully make the lang2nix packages work with Nixpkgs. I think this would achieve most of the benefits of what you propose: cleaner separation of infra vs vs ad-hoc per-package stuff, while still retaining the flexibility of the monorepo.

    The goal is to work with upstream developers so less and less ad-hoc crap is needed. Then the one repo ends up "all stdlib no packages", because the packages are basically autogenerated!

  • NixOS History and Our Experience - Nix, Null, Nada, Nothing
    8 projects | reddit.com/r/NixOS | 26 Jan 2022
    I changed it through this RFC. This was mostly to make easier to ship NixOS with the major DE's. The previous YY.03 and YY.09 schedule usually meant that were shipping almost EOL DE's in nix. The two month push back was so that the stable releases would be available for gnome (and plasma for YY.11), and we would have ample time to package and test them before release (Nixpkgs is purely volunteer based). Also avoided issues of having a version of systemd which Plasma and gnome weren't developed against: this caused issues like people not being able to switch user in plasma.
  • The Curse of NixOS
    35 projects | news.ycombinator.com | 24 Jan 2022
    I understand the first complaint but not the second

    > The second flaw is that NixOS does not actually provide real isolation.

    I thought this would going to be about security, but then it was about having to repackage the world. But Nixpkgs is current the biggest and most up to date package repository in the world (we finally beat AUR). Packaging enough stuff is emphatically not the problem.

    What I want to see is development be easier with Nix, because winning over the hearts and minds of upstream developers is the final frontier. To that end I wrote https://github.com/NixOS/rfcs/pull/92 and https://github.com/NixOS/rfcs/pull/109.

    As a side benefit, autogenerating more Nix means less handwritten Nix! I do think people give the language itself to much grief when the problem is more the library side with the copious override shenanagins and other stuff.

  • Proposal to add build graph output to GNU Make
    7 projects | news.ycombinator.com | 9 Jan 2022
    I would very much like this for https://github.com/NixOS/rfcs/pull/92
  • How would I override the version of llvm/compiler-rt?
    2 projects | reddit.com/r/NixOS | 30 Dec 2021
    Aarch64-darwin is still technically a Tier 7 platform: https://github.com/NixOS/rfcs/blob/master/rfcs/0046-platform-support-tiers.md
  • Is it worth learning and migrating to Flakes as of November 2021?
    3 projects | reddit.com/r/NixOS | 16 Nov 2021
    What makes you think so ? The only actual issue I had with flakes was the inability to import relative path flakerefs from the nix shell (which... is really easily solved, and may not actually be considered an issue). Flake semantic has pretty much been set in stone for the time I used it. It seemed pretty stable before the nix 2.4 release already, at least to me (I haven't noticed any real breaking change relevant to my use cases apart from the nix shell/nix run refactor), and with 2.4 I guess it's going to be even better. I don't expect the cli to change much (unless I've missed an announcement?), nor the way flakes work to have any breaking change (except maybe RFC 45, which will have some impact on a large number of flakes, even though it doesn't directly involves flakes).

What are some alternatives?

When comparing rfcs and rfcs you can also consider the following projects:

nix-ros-overlay - ROS overlay for the Nix package manager

nixpkgs - Nix Packages collection

nix-darwin - nix modules for darwin

spack - A flexible package manager that supports multiple versions, configurations, platforms, and compilers.

nix - Nix, the purely functional package manager

not-os - An operating system generator, based on NixOS, that, given a config, outputs a small (47 MB), read-only squashfs for a runit-based operating system, with support for iPXE and signed boot.

nixos-generators - Collection of image builders [[email protected]]

emacs-overlay - Bleeding edge emacs overlay [[email protected]]

NUR - Nix User Repository: User contributed nix packages [[email protected]]

asdf - Extendable version manager with support for Ruby, Node.js, Elixir, Erlang & more

nickel - Better configuration for less

Home Manager using Nix - Manage a user environment using Nix [[email protected]]