In reply to @Minijackson:matrix.org
wasn't there some efforts recently for adding vale to nix.dev? There's a lint for that

In reply to @proofconstruction:matrix.org
it would be great to be able to declare the style guide, and have that automatically checked (and ideally auto-corrected) everywhere

even though

❯ echo $NIX_PATH
nixpkgs=/nix/store/sd0xal2sd16vwgpba0z7cwr6zylp3axk-z6w242l49pbrdawkz5vdhfxh2mvsj36c-source

In reply to @nbp:mozilla.org
I do not want to be the devil advocate, but I just listen to an argument in a video roughly paraphrasing: "Due to the lack of proper documentation, Youtube videos about Nix are doing well"

That video seems to be about NixOS, in which case that statement is a fair assessment. NixOS documentation is certainly not in a good shape and essentially unmaintained content-wise.

Nixpkgs has a huge surface and we can barely scratch that with available capacity, but it’s very slowly getting better. There are also a lot of infrastructure issues, going deep down into the code.

Nix itself is much more manageable in terms of system size and complexity, so progress is more visible there. But there are the same kind of structural problems that really need to be addressed at the code level to unblock sweeping improvements documentation.

In reply to @nbp:mozilla.org
I do not want to be the devil advocate, but I just listen to an argument in a video roughly paraphrasing: "Due to the lack of proper documentation, Youtube videos about Nix are doing well"

except most community-based information of this sort is either:

1. wrong

2. propagating unhelpful practices

3. more of the "first we copy this" "then we paste this" variety