| 25 Jun 2021 |
 ash | ¯\_(ツ)_/¯ but nobody cares | 07:19:48 |
| ash | yeah nix documentation is a whole... thing | 07:20:09 |
 Jez (he/him) | which isn't to say that it isn't useful or well-written (it's both) but it won't teach you how to package something for nix | 07:20:21 |
| ash | i wish we promoted the wiki better | 07:20:28 |
| ash | did you know we used to have a wiki, and then that got abandoned and turned into the manual, and now we have a new wiki except not very much stuff is there | 07:21:03 |
| ash | but meh | 07:21:13 |
| ash | the new wiki feels like just a place to dump config snippets. i guess it's partly because nixos modules are self documenting and all | 07:22:18 |
| Jez (he/him) | that explains a lot about the manual too 😆 | 07:22:33 |
| Jez (he/him) | the configuration chapter in particular reads exactly like a dump of wiki content | 07:23:40 |
| ash | nix has a lot of... rough spots | 07:23:47 |
| ash | people are working on it | 07:24:13 |
| ash | if you wanna contribute to documentation that's always welcome and sorely needed | 07:24:28 |
| Jez (he/him) | In reply to @colemickens:matrix.org
maybe that's a sign it addresses a serious, real pain point? it's also that the main nix room's traffic has hit a point where it's hard to follow discussion and potluck whether your question gets answered or missed, and a solution to that is to bud off a new room for one or more specific topics | 08:13:32 |
| Jez (he/him) | in this case it seems like a room for flakes help would be useful, and another for flakes dev might help move the discussion forward | 08:14:02 |
 CRTified | In reply to @jez:petrichor.me
it's also that the main nix room's traffic has hit a point where it's hard to follow discussion and potluck whether your question gets answered or missed, and a solution to that is to bud off a new room for one or more specific topics And with spaces, splitting of a new room is not really harmful in the sense that it might dilute the community. That's one of the problems I've had with IRC - discoverability of new channels was "hard", especially when you're using a bridge from XMPP or Matrix for it. | 08:30:33 |
|  Valodim joined the room. | 11:55:18 |
 colemickens 🏳️🌈 | Here's the thing - I built my own pure eval pinning system, and just using flake.nix/flake.lock with flakes-compat with stable nix all works fine. | 17:59:50 |
| colemickens 🏳️🌈 | It works just fine. | 17:59:54 |
| colemickens 🏳️🌈 | * Here's the thing - I built my own pure eval pinning system, and moved to just using flake.nix/flake.lock with flakes-compat with stable nix all works fine. | 18:00:23 |
| colemickens 🏳️🌈 | * It works just fine. Given that flakes-compat + flakes.lock is effectively the exact same thing as manual pinning, I just don't really see removal as a path forward (though I do understand the frustration and reasoning) | 18:00:58 |
| ash | In reply to @colemickens:matrix.org
It works just fine. Given that flakes-compat + flakes.lock is effectively the exact same thing as manual pinning, I just don't really see removal as a path forward (though I do understand the frustration and reasoning) it would unblock the release pipeline | 18:13:38 |
| * colemickens 🏳️🌈 feels like he flip flops a lot too - even now part of me is like "ash is right and you know it, rip it out, start anew" | 18:21:07 |
| ash | like you said, if there's no harm done due to flakes-compat, then there's no reason not to | 18:23:16 |
| * colemickens 🏳️🌈 nods | 18:25:13 |
| Valodim | Make an rfc :) | 19:56:55 |
| Valodim | It sounds like the platform an agreement like that should happen on | 19:57:19 |
| colemickens 🏳️🌈 | 
Download image.png | 20:14:30 |
| colemickens 🏳️🌈 | nice, what's even happening here -> did my "/me nods" send? | 20:14:31 |
| colemickens 🏳️🌈 | oh great, a stuck message in element web, how shocking | 20:14:47 |
| CRTified | Yes, it's between those messages from ash and valodim for me | 20:15:13 |
