| 25 Jun 2021 |
 ash (it/its) 🏳️⚧️ | thank you for working on this stuff. it's valuable to try and deflate the problem, which i see you and others are working on doing | 03:41:42 |
| ash (it/its) 🏳️⚧️ | i get overly worked up about things like this, it's not only because of flakes but a general pet peeve of mine is people depending on unstable functionality | 03:42:35 |
| ash (it/its) 🏳️⚧️ | i can barely look at the main nix support channel because there's always someone asking for help with flakes and i hate it | 03:43:06 |
 David Arnold (blaggacao) | "deflate the problem" -- what a nice wording ! 😀 | 03:43:43 |
| ash (it/its) 🏳️⚧️ | making it smaller and more manageable, easier to remove fully in the future | 03:44:01 |
| David Arnold (blaggacao) | I'll put that in the UFR | 03:44:13 |
| ash (it/its) 🏳️⚧️ | i recognize that my ideal of getting rid of it in one fell swoop is maybe unrealistic | 03:44:26 |
| ash (it/its) 🏳️⚧️ | i do think it's the quickest way out but maybe not the most agreeable | 03:44:46 |
| David Arnold (blaggacao) | Here it is: https://demo.hedgedoc.org/uyQYTpTVQbyvpdcJ6MvlQg?view#Unofficial-Flakes-Roadmap | 03:45:04 |
| David Arnold (blaggacao) |
Lets deflate the problem
| 03:45:12 |
| David Arnold (blaggacao) | *
Lets deflate the problem ...
| 03:45:17 |
| David Arnold (blaggacao) | In reply to @kity:kity.wtf
i do think it's the quickest way out but maybe not the most agreeable I think with the right amount of deflation we can go back to a consensus point, indeed | 03:45:47 |
| David Arnold (blaggacao) | In reply to @kity:kity.wtf
i do think it's the quickest way out but maybe not the most agreeable * I think with the right amount of deflation we can go back to a consensus point, indeed 🤣 | 03:46:00 |
| ash (it/its) 🏳️⚧️ | i still stand by my statements of not caring what happens to flakes and just wanting them gone | 03:46:41 |
| ash (it/its) 🏳️⚧️ | so that's the point i want to reach | 03:46:48 |
| ash (it/its) 🏳️⚧️ | and maybe when they're reintroduced through a proper process i'll be more comfortable with it all | 03:47:20 |
| ash (it/its) 🏳️⚧️ | if you want my real opinion, i think unstable nix should not be in nixpkgs at all, nor should nix flakes | 03:49:34 |
| ash (it/its) 🏳️⚧️ | one should have to go out of their way to get an unstable version of nix directly from the nix repo, because they're working on its development | 03:50:13 |
| ash (it/its) 🏳️⚧️ | having it so easily accessible promotes use of unstable features, which influences workflows and results in dependence on unstable stuff | 03:51:14 |
| ash (it/its) 🏳️⚧️ | maybe i'm wrong. idk | 03:51:19 |
| David Arnold (blaggacao) | It's diabolic poitics at play 😁 | 03:55:20 |
 colemickens | Redacted or Malformed Event | 06:39:51 |
| colemickens | Redacted or Malformed Event | 06:40:10 |
| colemickens | Redacted or Malformed Event | 06:42:20 |
| colemickens | same ole flakes FUD | 06:42:45 |
| colemickens | In reply to @kity:kity.wtf
i can barely look at the main nix support channel because there's always someone asking for help with flakes and i hate it maybe that's a sign it addresses a serious, real pain point? | 06:43:40 |
| colemickens | "having it so easily accessible promotes use of unstable features, which influences workflows and results in dependence on unstable stuff" | 06:48:11 |
| colemickens | .... is there an actual example? | 06:48:20 |
 Jez (he/him) | I feel like a big part of the problem is that so much of the knowledge of how nix works and how to use it exists only in the heads of community members | 07:00:33 |
| Jez (he/him) | The documentation is structured such that even if what you want to know is documented, it's really hard to find | 07:01:23 |
