Comments by "" (@traveller23e) on "Fireship"
channel.
-
166
-
143
-
61
-
55
-
37
-
36
-
35
-
34
-
32
-
32
-
31
-
30
-
30
-
27
-
25
-
24
-
24
-
23
-
21
-
17
-
17
-
16
-
15
-
12
-
12
-
11
-
11
-
10
-
10
-
9
-
9
-
9
-
9
-
9
-
8
-
8
-
8
-
8
-
7
-
7
-
7
-
7
-
I have Arch on one machine, NixOS on another. They have fundamentally different use-cases.
Arch is fantastic if you're decently good at configurations and have a single machine you frequently need to adjust settings on, especially thanks to its incredible docs. It also does a pretty good job of ensuring you don't end up with meaningless duplicate packages. However, if you want any kind of partitioning of program installation it starts to work against you, e.g. it's easy installing a program on the system but hard to install it for just one user. It's also hard to install multiple versions of stuff if you need that (not normally a problem but it could be). Additionally, in a fairly normal install it's more or less incompatible with Haskell development due to the fact that by default Arch uses dynamically linked libraries and Haskell revolves around statically linked ones (technically options for dynamic linking exist, but mileage may vary and to give an idea some related critical bugs have sat unfixed for years).
I installed nixOS for the facility of operations with Haskell, and I can see how it would be great if you needed to install identical systems on multiple computers. It allows having packages installed only when you're in certain environments making it really easy for groups to share their build dependencies, however what's not mentioned in the video is that understanding how any of that works is very difficult due in large part to lack of clear guides and when there is documentation it tends to only cover one small part of the setup so it's up to you to figure out how the components work together. Additionally, if you're doing a lot of tweaks to your config firstly they take forever to test and secondly you'll quickly end up with lots of different versions of your machine each with its own set of binaries etc. Of course you can clean that up. The other thing is that although the versioning saves the state of your installed programs, it does not save the state of your homefiles which could easily include configs written by those same programs so it could be rolling back doesn't restore some data deleted or updated in the interim.
7
-
7
-
6
-
6
-
6
-
6
-
5
-
5