| 17 Mar 2025 |
 balanced_design | I dont know if "until it makes sense" is the problem. To solve these problems Ive just had to figure out what the actual correct thing is because the instructions on the docs, form posts, or blog posts are wrong or have multiple interpretations. Ive had few errors due to my own stupidity or something else like that | 06:30:39 |
| balanced_design | Some blog posts have mentioned that. It does seem like nix has cheetsheets like other programing languages | 06:31:45 |
| balanced_design | * I dont know if "until it makes sense" is the problem. To solve these problems Ive just had to figure out what the actual correct thing is because the instructions on the docs, form posts, or blog posts are wrong(causes errors or dont work) or have multiple interpretations. Ive had few errors due to my own stupidity or something else like that | 06:32:00 |
| balanced_design | * Some blog posts have mentioned that. It does seem like nix has cheatsheets like other programing languages | 06:32:09 |
| balanced_design | * Some blog posts have mentioned that.It does seem like nix has cheatsheets like other programing languages | 06:32:20 |
| balanced_design | * Some blog posts have mentioned that.
It does seem like nix has cheatsheets like other programing languages | 06:32:30 |
| balanced_design | * I dont know if "until it makes sense" is the problem. To solve these problems Ive just had to figure out what the actual correct thing is because the instructions on the docs, form posts, or blog posts are wrong(causes errors or dont work) or have multiple interpretations. Ive had few errors due to anything that feels like "oh it just hadnt clicked". | 06:33:33 |
| balanced_design | * I dont know if "until it makes sense" is the problem. To solve these problems Ive just had to figure out what the actual correct thing is because the instructions on the docs, form posts, or blog posts are wrong(causes errors or dont work) or have multiple interpretations. I havent had any errors due to anything that feels like "oh it just hadnt clicked". | 06:34:27 |
 K900 | Well the thing is, after it clicks, it'll be generally much easier for you to figure out why something isn't working | 06:34:51 |
| balanced_design | Thats reasonable I could see that being a possibility. | 06:37:55 |
| balanced_design | As far as I understand based on https://search.nixos.org/packages I need unstable to get fully up to date packages | 06:38:22 |
| K900 | Then you should switch your entire system to run on unstable, generally | 06:38:39 |
| K900 | Mixing channels is rarely a good idea | 06:38:45 |
| balanced_design | Wait why? Why would packages accross channel boundries interact in a bad way? | 06:39:37 |
| K900 | There are, uh, quirks | 06:42:10 |
| K900 | Notably around how we handle graphics drivers | 06:42:19 |
| K900 | But there can also be others | 06:42:25 |
| K900 | The core problem is that you can't really have two copies of the same library loaded into the same process | 06:42:54 |
| balanced_design | Is unstable supposed to be combined with something that allows you to select the package version stable would give you? | 06:43:03 |
| K900 | So anything that relies on dynamically loaded plugins, or library injections, etc, can get REALLY confused | 06:43:15 |
| K900 | Not really, no | 06:43:20 |
| K900 | "Unstable" is just a bad name | 06:43:29 |
| K900 | It's not unstable as in "has bugs" | 06:43:33 |
| K900 | It's unstable as in "has no stable API" | 06:43:43 |
| K900 | But even that is kind of an exaggeration | 06:43:51 |
| K900 | It's not any more "unstable" than any other rolling release distro | 06:44:00 |
| balanced_design | API as in options correct? | 06:44:16 |
| K900 | Primarily | 06:45:27 |
| K900 | And generally we try really hard to not just break people in confusing ways | 06:45:45 |
| K900 | So usually when an option is changed there's a migration period and a warning | 06:45:55 |
