niv
rnix-lsp
Our great sponsors
niv | rnix-lsp | |
---|---|---|
16 | 7 | |
1,456 | 695 | |
- | - | |
6.3 | 0.0 | |
about 2 months ago | 4 months ago | |
Haskell | Rust | |
MIT License | MIT License |
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.
niv
-
NixOS + Haskell best practices circa March 2023
niv
-
Pulling themes from a git project: the nix way?
Flakes work. An alternative is niv which was once popular and provides a good developer experience.
-
What are the biggest Pain Points with NIX? And what makes it worth the pain?
Essentially you can just think of it as a standardized default.nix/shell.nix with built-in Niv integration.
-
Our Roadmap for Nix
I agree that the FP part is not the only issue. It's that the community feels a bit more academic/I'll fix this for myself in the way that works best for me.
You can indeed achieve some reproducibility with Docker. It's tricky though, as you'd have to pin exact package versions of software. If you'd `FROM ubuntu:$VERION`, and would run an `apt-get update`, you're not guaranteed to get the same software.
Nix is like ZFS, as that it breaks the wall between two previously distinct area's. Those being building software, and installing/configuration software on your OS. It's quite different from the snapshot-everything methodology that Docker uses. Yeah, one can split in multi-stage images etc, but than you'll be keeping track of which dependencies need to be moved between the stages yourself, in a manner that cannot be abstracted away, so you're doomed to repeat the same patterns over and over again.
People also state that LVM + ext3 is more than sufficient compared to the complexity of ZFS. They miss out on the fact on how much more fine grained solutions are possible with ZFS.
I've used niv [0] before flakes arrived, and am actually still using that instead of flakes. The experimental nature of them has scared me away from them, as I'm not daily involved in this ecosystem at the moment.
[0] https://github.com/nmattia/niv#niv
-
Simplest way to set up neovim
You can use something like Niv to manage additional sources. I use it to fetch some Emacs packages, for example ligature.el. Then you update the package using $ niv update.
-
Unstable vs Stable channels
One thing that made this easier was switching from using Nix channels to explicitly pinning my dependencies with Niv. I honestly never fully understood how channels worked, and it's just much nicer to have everything specified in my Git repo. The exact commit of Nixpkgs that I'm using is in my sources.json file, so "reverting" just means checking out an older commit of my configs from Git then running nixos-rebuild switch. If I were redoing my dotfiles today I'd probably use Nix Flakes rather than Niv, but I suspect that Niv is still an easier option to get started with.
-
Remove unused niv packages
Does someone know of a way to remove unused pinned packages via [niv](https://github.com/nmattia/niv)?
-
How to downgrade single package?
Pin nixpkgs, and version control it. If you're using flakes, then just version control the flake.lock alongside your configuration. If you're not using flakes, you can use niv to easily pin nipxkgs, at the expense of some boiler plate.
- Compiling emacs is killing me
-
Ditch Your Version Manager
This... This is laughable. How do I install ruby 2.6.8? Oh, there's no ruby_2_6_8, because of course there isn't. And this could be difference between a secure system and all your base are belong to us.
And they call this reproducible builds?
And that's before getting into the ridiculous
--- start quote ---
All the software that we installed depends on the specific version of the nixpkgs channel that we installed on our system [whose only version is a commit hash in a git repo]
--- end quote ---
So you need an extra tool [2] for, quote, "painless dependencies for Nix projects."
Yes, sure. I'm definitely ditching my version managers in favor of this tool, that hasn't solved these issues in 18 years of its existence.
[1] https://search.nixos.org/packages?channel=21.05&from=0&size=...
[2] https://github.com/nmattia/niv
rnix-lsp
-
Editor support for the nix language?
There's a work in progress language server: rnix which I'm using in emacs. Features like autocomplete are limited though, I'm guessing because you'd need to evaluate the actual Nix code to correctly deduce what properties exist.
-
What are the biggest Pain Points with NIX? And what makes it worth the pain?
There’s rnix-lsp.
- Our Roadmap for Nix
-
Rust Environment and Docker Build with Nix Flakes
https://github.com/nix-community/rnix-lsp works ok, it has some autocomplete but it does not infer options most packages expose unfortunately.
- rnix-lsp not working with an m1 mac in macos:
-
Statix — Lints and Suggestions for the Nix programming language
Looks cool! Any thoughts on the relationship between Statix and https://github.com/nix-community/rnix-lsp ?
- Nix-GUI: Make NixOS usable for non-technical users through settings / GUI
What are some alternatives?
leksah - Haskell IDE
nickel - Better configuration for less
update-nix-fetchgit - A program to automatically update fetchgit values in Nix expressions
nixos-hardware - A collection of NixOS modules covering hardware quirks.
ghcid - Very low feature GHCi based IDE
git-hooks.nix - Seamless integration of https://pre-commit.com git hooks with Nix.
elm-make
nix-direnv - A fast, persistent use_nix/use_flake implementation for direnv [maintainer=@Mic92 / @bbenne10]
hpc-threshold - Small utility for validating whether HPC result is above defined thresholds
nixos-nvidia-vgpu - NixOS NVIDIA vGPU Module
ihaskell - A Haskell kernel for the Jupyter project.
nix-config - :space_invader: NixOS configuration