rnix-parser
nickel
rnix-parser | nickel | |
---|---|---|
3 | 46 | |
339 | 2,170 | |
3.2% | 3.6% | |
0.0 | 9.5 | |
13 days ago | 4 days ago | |
Nix | 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.
rnix-parser
-
auto update notifier & gui for non-tech users?
I definitely plan to support as much as I can, but there is definitely a level of complexity that can never be truly translated to a graphical tool. What I've found helpful during development for me is that I split the frontend GUI and the backed parser and editor into two projects (nixos-conf-editor and nix-editor), that way I could tackle a lot of the parsing and editing alone without worrying about specific GUI features needed (and use it for other projects). Later when I need some feature I add it to nix-editor. So far nix-editor supports simple attribute modification, array adding and popping, and recursive attribute definition and dereferencing. It's definitely not perfect by any means, but so far it's been enough for the projects I've been working on. I definitely need to credit any success I've had so far to the developers of rnix-parser which translates nix expression to easy to manage ASTs.
-
Advantages of flakes
I'm hopeful that with https://github.com/nix-community/rnix-parser being a thing now, we can get some better Nix tooling, particularly for stuff like linting and doc extraction.
-
The Curse of NixOS
Okay, yes, I agree with all of that. Flakes are kind of a module system, but having clearer semantics around functions and classes would definitely help with both code readability and producing better stack traces.
And a proper type system would be awesome.
Regarding docs, it is interesting that portions of the nixpkgs source do seem to have docblock-like comments above the functions, but AFAICT there's no formalized process for extracting or rendering those. Given that https://github.com/nix-community/rnix-parser exists, I wonder how big of a leap it would be to actually extract those, render them into rST pages, and generate a searchable Sphinx manual.
nickel
-
Nix – A One Pager
So, its key features are:
1. domain-specific: designed for conveniently creating and composing derivations. This reason alone already justifies a new language, or an embedded domain-specific language (such as the Guile/Scheme for guix), or a mix of both (Starlark, the build language of Bazel embedded in a restricted Python-variant).
2. purely functional: this ties well into the philosophical backing of Nix the package manager, which aims to be purely functional, also known as hermeticity in other build systems (Bazel).
3. lazily evaluated: similar to other build systems (including Bazel), so that you can build only what you need on demand.
4. dynamically typed: this one is controversial. Being dynamically typed—in other words, not developing a type system—gets Nix out of the door first. But users often complain about the lack of proper types and modularity. There are experiments to address this, such as Nickel (https://github.com/tweag/nickel).
It is understandable that a one-pager may not have space for the whys.
-
10 Ways for Kubernetes Declarative Configuration Management
Nickel:Nickel is a straightforward configuration language aimed at automatically generating static configuration files. Essentially, it's akin to JSON with the addition of functions and types.
-
Show HN: Togomak – declarative pipeline orchestrator based on HCL and Terraform
Also look at nickel which is an evolution of nix. It's my favorite in this space.
nickel-lang.org
https://github.com/tweag/nickel
- Show HN: Flake schemas – teaching Nix about your flake outputs
-
What config format do you prefer?
Or this https://github.com/tweag/nickel
-
Nickel 1.0
Nickel is a programming language. While HCL is just a configuration format, so not really comparable.
Here's a comparison with similar tools: https://github.com/tweag/nickel#comparison
-
Announcing Nickel 1.0, a configuration language written in (and usable from) Rust
As for 'providence', I suppose you meant provenance :) it's been delayed because this was less critical for 1.0 to decide on or to implement (as it: it doesn't break backward compatibility in any way to add this feature in the short term), but this is very much on the roadmap: Issue #235. That's a must-have in a language with merging like Nickel.
-
Rewrite it in Rust: Kubernetes
Have you considered using a different language for templating? this could be a BIG selling point. Some good ones are cue-lang (though I haven't seen support for rust), kcl or nickel-lang.
- Nickel v1.0.0
- Design rationale for the Nickel configuration language
What are some alternatives?
Nixos-Gui - Gui for Nixos package manager
rnix-lsp - WIP Language Server for Nix! [maintainer=@aaronjanse]
supertux - SuperTux source code
nixos - My NixOS Configurations
nix - Nix, the purely functional package manager
nix-gui - Use NixOS Without Coding
nvd
nix-doc - An interactive Nix documentation tool providing a CLI for function search, a Nix plugin for docs in the REPL, and a ctags implementation for Nix script
nix-editor - A simple rust program to edit NixOS configuration files with just a command
AppImageKit - Package desktop applications as AppImages that run on common Linux-based operating systems, such as RHEL, CentOS, openSUSE, SLED, Ubuntu, Fedora, debian and derivatives. Join #AppImage on irc.libera.chat
system-updater - Systemd services for checking for and applying system updates.