this post was submitted on 24 Jan 2024
105 points (95.7% liked)
Linux
48044 readers
777 users here now
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Rules
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
founded 5 years ago
MODERATORS
There is controversy in the nix world because nix flakes were (some say) merged without proper vetting first. OG nix diehards don't want to taint nix documentation with 'experimental' flakes. But probably the majority of nix users are all in on flakes. So you have documentation from the OG camp that doesn't include flakes, and you have innumerable unofficial guides for the flakes way. This on top of the quirkiness of nix the language and the multiple ways to do things. Unfortunate.
IMO nix-env was a mistake. It feels like an imperative package manager which may be comfortable to new users who are used to apt or similar. But really what you should be doing on nix is maintaining *.nix files which document/specify your system setup, and nixos-rebuild to update your system to that configuration. Similarly, nix channels are an imperative holdover, which can be done away with if you use flakes, which results in your current nixpkgs version being documented in a system level flake.lock file.
I think both nix-env and flakes are designed with making package management easier. Nix-env tries to make it intuitive and familiar for new users. Flakes improve package management by simplifying the configuration.
Personally I would love to see syntax highlighting, language server, code completion. Maybe all in a dedicated application which is configured to give the easiest experience for new users. If nix is intended to be managed through config files, then the experience of writing a config should be as easy as possible.
The intent of nix-env was to make it easier, but the effect was to push some of your system state into a shadowy 'env' realm that is not managed by your *nix files. Same with channels - its state that isn't in your configuration.nix.
To me the whole point is to have all your state in some files you can check in to version control, and use to reproduce your system.
Agree it would be cool to have a way to edit nix files that would give you all the args to functions, code completion etc. You do get some of that with the nix repl. Would be nice to even have a GUI for selecting packages for those that don't "do" text editing.
I'm using nixd for a nix language server, but haven't seen a lot of benefit so far to be honest. I think part of the reason is nixpkgs isn't pulled in until runtime, so most things are undefined as far as the lsp is concerned. Haven't put a lot of time into it, there may be ways to make it more useful.
Syntax highlighting, LSP and code formatting work flawlessly for me using Helix, and therefore should on any editor that implemented LSP