| 17 Mar 2025 |
 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 |
