| 13 Aug 2022 |
| *  pennae better shut up now | 03:19:41 |
|  yuu changed their display name from yuu[m] to yuu. | 05:06:10 |
 John Ericson | So seeing more progress with Tvix and https://github.com/nix-community/go-nix, I am more willing to have things out of tree | 12:25:43 |
| John Ericson | Should check with fricklerhandwerk though | 12:26:01 |
| John Ericson | (My interpretation is that the landed arch section and my changes basically have the same issues from Eelco's perspective) | 12:32:28 |
| 15 Aug 2022 |
 Gytis Ivaskevicius | I thought tvix is dead π€ | 10:47:20 |
| John Ericson | Gytis Ivaskevicius: it was just on private branches I guess | 13:22:33 |
| 17 Aug 2022 |
|  ε€ει
| Yorusaka Miyabi left the room. | 02:11:08 |
|  -=h0p3=- joined the room. | 03:40:47 |
 olaf | another PR to look at (part of the attempt to provide introduction to nixos configuration documentation):
https://github.com/NixOS/nix.dev/pull/305/files | 10:36:40 |
| olaf | * another PR to look at. it is part of the attempt to provide introduction to nixos configuration documentation:
https://github.com/NixOS/nix.dev/pull/305/files | 11:10:45 |
 Sandro π§ | nix.dev got moved to NixOS? We might as well remove the lines from anti-patterns that are not in line with the contributing guide of nixpkgs. | 11:48:04 |
| Sandro π§ | Then reviewers no longer need to fight against half correct recommendations | 11:48:50 |
| Sandro π§ | https://github.com/NixOS/nix.dev/pull/307 | 11:54:59 |
 luxus | one issue with nix i run more then 1 time into it.. there are many tools to tackle a problem. and no central site with infos (or i didn't found it yet) two examples are deploy and secrets. i wish i would have. secrets.md that list all options to handle secrets in best case with comparison | 14:56:43 |
 fricklerhandwerk | @luxus There is this NixOS Wiki page: Comparison of secret managing schemes
Otherwise you're right, and Domen KoΕΎar said the same in his talk yesterday. Converging on recommendations for best practices is something that nix.dev is meant to do, and the Nix documentation team will support all efforts in that direction.
| 15:13:53 |
| luxus | and its a selling point as well.. if we have a overview of features.. it takes a moment to find out about flakes, home-manager, secrets and the benefits | 15:15:26 |
| luxus | not to talk about cool fancy rice stuff like stylix or nix-colors π | 15:16:05 |
| luxus | linux have distro hopping .. nix itself have solution hopping .. | 15:17:10 |
| luxus | starting with a configuration.nix switching to flake.nix switching to a flake that you find on github. switching to another one.. deciding to write your own flake again .. | 15:18:03 |
| luxus | finding a flake configuration that have a similar setup makes understanding so much easier. and frameworks like digga are really hard to understand in the first try | 15:20:07 |
| luxus | sorry english is not my native tongue π i just talking about my experiences from the last year | 15:20:55 |
 tpw_rules | imho, and i've expressed this to various people looking for help, flakes have been overcomplicated | 15:21:26 |
| luxus | yes.. and as soon you use a flake config that use some homemade libs, most instructions on websites are not working anymore | 15:22:40 |
| luxus | its really hard to write a config only with the understanding for programing. its a big plus to understand the nixlang... and i normally can hack my why into most stuff π i can use/create/modify neovim configs in lua without speaking lua. i can fix python stuff without fully understand python.. but with flakes i really feel lost | 15:25:31 |
|  pedrohlc left the room. | 18:32:41 |
|  greaka joined the room. | 20:21:33 |
| 18 Aug 2022 |
|  Paul Tiplady joined the room. | 03:07:05 |
| Paul Tiplady | Hi folks, Nix noob here, I have a few small thoughts about rough edges on the "new user experience" where some aspects of the docs took me 5-10 mins of digging where I feel they could have been structured to hand-hold a bit better. I've just gone through the Rust Book and so I've got some good contrast for how nice a ramp-up doc can be. Is it useful to share nits and other suggestions here? I feel like most of my input is too small to justify a Github issue. | 03:10:43 |
| tpw_rules | i'd say go ahead | 03:18:54 |
