⛩️ Powerful yet Minimal Nix Dependency Manager
flake
flakes
home-manager
nixos
go
nix
dependency
dependencies
docs(readme): reword hook points
+23
-3
+23
-3
README.md
+23
-3
README.md
···
6
6
<details closed>
7
7
<summary>Why should I consider Yae over niv or <code>npins</code>?</summary>
8
8
9
-
1. No BS helper Nix expressions are needed by Yae. niv and `npins` spit out unnecessary and mostly complicated Nix expressions by default in the form of a file that you need to keep in sync with their mainline source. This requires additional upgrade commands from the CLI and more to maintain. A Yae environment is a single file and can be placed anywhere.
10
-
2. Yae has a simple and coherent source tree. niv has a total of 10000 LOC (lines of code), `npins` sits at almost 6000 LOC flat, and Yae stands at just shy of 1500 LOC when looking at all files. Yae's core source code itself sits at just 462 LOC, which is much, **much** smaller than that of niv and `npins`' core source trees. This is all to say that Yae implements everything needed to replace niv and `npins` in a much more efficient and concise codebase.
9
+
1. No unnecessary helper Nix expressions are needed by Yae.
10
+
11
+
niv and `npins` spit out medium-to-large sized Nix expressions that vary in
12
+
complexity in the form of a file that you need to keep in sync with their
13
+
mainline sources. This requires additional upgrade commands in the CLI and
14
+
more effort to maintain. A Yae environment is a single file and can be placed
15
+
anywhere and read just as simply.
16
+
2. Yae has a simple and coherent source tree. niv has a total of 10000 LOC
17
+
(lines of code), `npins` sits at almost 6000 LOC flat, and Yae stands at just
18
+
shy of 1500 LOC when looking at all files. Yae's core source code itself sits
19
+
at just 462 LOC, which is much, **much** smaller than that of niv and `npins`'
20
+
core trees. This is all to say that Yae implements everything needed to functionally
21
+
replace niv and `npins` in any workflow, and in much more efficient and concise
22
+
codebase.
11
23
3. Yae is simple by nature in design and usage philosophy.
12
24
13
-
niv and `npins` are great, but are far too ~~overkill~~ overengineered for me and many other consumers. I say overengineered because I was able to write out Yae's initial implementation in just about thirty-minutes to an hour, and it was already complete enough for me to replace niv or `npins` in all of my production workflows. If you need some niche feature that niv or `npins` have, use them, but if not, Yae is here for you.
25
+
niv and `npins` are great, but are far too ~~overkill~~ overengineered for me
26
+
and many other consumers. I say overengineered because I was able to write out
27
+
Yae's initial implementation in just about thirty-minutes to an hour, and it
28
+
was already complete enough for me to replace niv or `npins` in all of my production
29
+
workflows. If you need some niche feature that niv or `npins` has, use them,
30
+
but if not, Yae is here for you.
31
+
14
32
</details>
15
33
16
34
## Introduction
···
102
120
};
103
121
}
104
122
```
123
+
105
124
</details>
106
125
107
126
### Integrating with Nix
···
162
181
# inherit (yae.zen-browser-twilight-bin) sha256 version;
163
182
} { inherit pkgs; }
164
183
```
184
+
165
185
</details>
166
186
167
187
## `--help`