purenix
rfcs
Our great sponsors
| purenix | rfcs | |
|---|---|---|
| 4 | 46 | |
| 281 | 487 | |
| 1.8% | 5.3% | |
| 2.1 | 5.0 | |
| 4 months ago | 5 days ago | |
| Haskell | ||
| BSD 3-clause "New" or "Revised" License | Creative Commons Attribution Share Alike 4.0 |
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.
purenix
-
Nix: An idea whose time has come
There’s also the PureNix project that lets you go from PureScript→Nix. Caveats in the docs.
- PureNix: Compile PureScript to Nix
- PureNix: Transpile PureScript Code to Nix
- The Curse of NixOS
rfcs
-
Build System Schism: The Curse of Meta Build Systems
Nix with dynamic derivations (RFC92) could potentially beat this curse.
https://github.com/NixOS/rfcs/blob/master/rfcs/0092-plan-dyn...
-
Show HN: Flox 1.0 – Open-source dev env as code with Nix
See: A plan to stabilize the new CLI and Flakes incrementally https://github.com/NixOS/rfcs/pull/136
- RSS can be used to distribute all sorts of information
-
I like gentoo's package deprecation process
NixOS recently introduced "problem" infrastructure to deal with such problems more gracefully and explicitly:
https://github.com/NixOS/rfcs/blob/master/rfcs/0127-issues-w...
-
NixOS and Flakes Book: An unofficial book for beginners (free)
For some more context: Flawed as they are, Flakes solve a large number of problems Nix experiences without them. This is why I, and presumably many others, use them even in their current experimental state.
An RFC was recently accepted to commit to forming a plan towards stabilization of Flakes: https://github.com/NixOS/rfcs/pull/136
Personally, I don't believe there won't be any breaking changes, but I also believe that the stabilization of Flakes is still a ways away and hope that there will be a reasonable migration path.
- NixOS RFC 136 approved: A plan to stabilize the new CLI and Flakes incrementally
- NixOS RFC 136 accepted: A plan to stabilize the new CLI and Flakes incrementally
-
The NixOS Foundation's Call to Action: S3 Costs Require Community Support
NixOS needs to merge https://github.com/NixOS/rfcs/pull/133 to solve the issue
- Bootspec
-
Super Colliding Nix Stores: Nix Flakes for Millions of Developers
> Afterwards, Flakes itself and its CLI components can be stabilized. The final design of Flakes will also require another RFC.
That seems like Flakes are still quite a ways away.
[1] - https://github.com/NixOS/rfcs/pull/136
First, the non-Flakes CLI wll be stabilized, in phases.
What are some alternatives?
onyx - Toolkit for converting and building songs for Rock Band, Guitar Hero, Clone Hero, and other similar rhythm games
nix-ros-overlay - ROS overlay for the Nix package manager
nickel - Better configuration for less
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.
spack - A flexible package manager that supports multiple versions, configurations, platforms, and compilers.
nixpkgs - Nix Packages collection & NixOS
devshell - Per project developer environments
nix - Nix, the purely functional package manager
nixpkgs-config - ~/.config/nixpkgs
aconfmgr - A configuration manager for Arch Linux
emacs-overlay - Bleeding edge emacs overlay [maintainer=@adisbladis]