Nix Documentation | 436 Members | |
| Discussion about documentation improvements around the Nix ecosystem | 92 Servers |
| Sender | Message | Time |
|---|---|---|
| 13 Jul 2023 | ||
| 08:27:44 | ||
| 22:02:48 | ||
| 16 Jul 2023 | ||
| 02:36:59 | ||
| 17 Jul 2023 | ||
Download 2023-07-17-120337_917x440_escrotum.png | 11:03:44 | |
Download 2023-07-17-120427_830x571_escrotum.png | 11:04:36 | |
| quite consistent results over different social media | 11:05:03 | |
| Is that really debatable at this point? It *should* teach about them. It should just also explain that they're still an experimental feature. | 12:46:44 | |
| I've seen that the team decided not to touch flakes and I think that's the wrong direction, given what people are using these days. | 14:39:20 | |
| It is indeed what we agreed upon at the moment, given that they're marked as experimental. We decided to only focus our (limited) energies on what's stable, and to defer to the wider community for when flakes are ready for prime time. There are obvious downsides to this, and different ways to look at the situation (one of them being "harm reduction", i.e. people are already using them, we should teach them how to do it safely), but given that the state of the conversation is what it is, the team opted for having a clearly defined line between what's supported and what isn't | 14:45:41 | |
| * It is indeed what we agreed upon at the moment, given that they're marked as experimental. We decided to only focus our (limited) energies on what's stable, and to defer to the wider community for when flakes are ready for prime time. There are obvious downsides to this, and different ways to look at the situation (one of them being "harm reduction", i.e. people are already using flakes, we should teach them how to do it safely), but given that the state of the conversation is what it is, the team opted for having a clearly defined line between what's supported and what isn't | 14:47:43 | |
| * It is indeed what we agreed upon at the moment, given that they're marked as experimental. We decided to only focus our (limited) energies on what's stable, and to defer to the wider community for when flakes are ready for prime time. There are obvious downsides to this, and different ways to look at the situation (one of them being "harm reduction", i.e. people are already using flakes, we should teach them how to do it safely), but given that the state of the conversation is what it is, the team opted for using stability as the demarcating line between what goes into nix.dev and what doesn't | 14:48:32 | |
| We could make it a sprint topic for nixcon :) | 14:53:00 | |
In reply to @domenkozar:matrix.orgcould be an idea 🙂 unfortunately tickets already sold out ☹️ | 14:55:23 | |
| I'll be there and I'd rather focus on docs infrastructure, such as setting up better linting and automated tests for examples | 15:04:27 | |
| * I'll be there and I'd rather focus on docs infrastructure, such as setting up better linting and automated tests for examples, as that will provide long-term value regardless | 15:04:44 | |
| Domen Kožar: I really like the idea of "If you want Flakes to be officially documented, work towards its stabilisation" | 15:34:42 | |
| It doesn't make sense to invest a lot of effort into documenting something experimental, but not investing effort into trying to stabilise it | 15:35:08 | |
| asymmetric: pinged you privately to get this resolved! :) | 16:55:02 | |
In reply to @infinisil:matrix.orgMost of Nix users are using flakes and it's not documented, that's what I care about. The stabilization process is something I'm personally not interested to put in the time, I care that our users have docs to use Nix :) | 17:11:26 | |
| I'm fine saying it's experimental, etc. | 17:12:06 | |
| It's experimental for a reason, Flakes still has a number of major problems left unaddressed | 17:12:25 | |
| I do not want these to become immortalized | 17:12:38 | |
| That's really orthogonal, most users use flakes, that's the interface they expect. | 17:12:53 | |
| Either way, if we make changes it will be V2. | 17:13:07 | |
| I'd rather have well-designed software than many users. The better something is designed, the longer it will last because it's harder for something better to replace it | 17:16:39 | |
| What I'm saying is that's not the reality we live in. We can talk about dreams, but there are a lot of Nix Flakes users that need documentation to be able to use it. | 17:17:07 | |
| There were many mistakes made on the path of flakes, but not having the docs is something we need to fix asap. | 17:18:04 | |
| Yeah I get it, that's just not where my priorities are. There's more dire problems to solve than to document hacked-together experimentally-labeled features | 17:18:52 | |
| * Yeah I get it, that's just not where my priorities are. I think there's more dire problems to solve than to document hacked-together experimentally-labeled features | 17:19:30 | |
| I lean more Domen Kožar's direction on this one for the simple reason that the majority of my 2 years with Nix has been flake-oriented. The only time I write a shell.nix is to make a project compatible for non flake users. There are valid concerns about flakes and a need to stabilise them. Maybe I'm putting effort in the wrong place and should be helping to stabilise flakes like you said infinisil rather than putting effort into documenting a workflow I choose not to use on a daily basis (and I say this without any kind of snark or ill feeling). | 18:13:02 | |