| 27 Dec 2025 |
Emma [it/its] | i dont think you'd want your machines to be on different nixpkgs versions because there's a 5 minute difference between when they were deployed | 15:16:08 |
| ---m--- set a profile picture. | 15:25:39 |
@acidbong:envs.net | also faster to build closures, cuz they'll share like 80% of derivations | 16:03:55 |
@acidbong:envs.net | at least | 16:04:19 |
daslixou | Hello!
I'm Lixou and recently got dragged to the idea of playing with linux systems again.
Now, because I am so smart that I directly from the first second on knew a whole own pacman and distro would be a bit much, I thought about helping here instead. (My main reasons for my own distro experiment were that I find nix unreadable in some places and that I thought nix would easily install 20 versions of a lib because well "reproducable" instead of just the newest, which I know now is not the case ^^')
So I don't have much experience with nix, but some with linux and heard that you have some clear visions for nix' future and want to port/rewrite the parser in rust.
Yeah idk how to end this, I'm just silly :3 I love rust and have way too many projects but some contributions to another rust parser are certainly missing. So if there's a broad idea and issues to the parser, I could help :) | 16:04:49 |
@acidbong:envs.net | the big point of flakes (or any other pinning system) is exactly the presence of a lockfile | 16:05:15 |
daslixou | * Hello!
I'm Lixou and recently got dragged to the idea of playing with linux systems again.
Now, because I am so smart that I directly from the first second on knew a whole own pacman and distro would be a bit much, I thought about helping here instead. (My main reasons for my own distro experiment were that I find nix unreadable in some places and that I thought nix would easily install 20 versions of a lib because well "reproducable" instead of just the newest, which I know now is not the case ^^')
So I don't have much experience with nix, but some with linux and heard that you have some clear visions for nix' future and want to port/rewrite the parser in rust.
Yeah idk how to end this, I'm just silly :3 I love rust and have way too many projects but some contributions to another rust parser are certainly missing. So if there's a broad idea and issues to the parser, I could help :)
(also I'm Lixou and Lix is called Lix, so that's funny) | 16:05:17 |
daslixou | * Hello!
I'm Lixou and recently got dragged to the idea of playing with linux systems again.
Now, because I am so smart that I directly from the first second on knew a whole own pacman and distro would be a bit much, I thought about helping here instead. (My main reasons for my own distro experiment were that I find nix unreadable in some places and that I thought nix would easily install 20 versions of a lib because well "reproducable" instead of just the newest, which I know now is not the case ^^')
So I don't have much experience with nix, but some with linux and heard that you have some clear visions for nix' future and want to port/rewrite the parser in rust.
Yeah idk how to end this, I'm just silly :3 I love rust and have way too many projects but some contributions to another rust parser are certainly missing. So if there's a broad idea and issues to the parser, I could help :)
(also I'm Lixou and Lix is called Lix, so that's funny) ((I know I lack humor)) | 16:05:38 |
K900 | There is some work ongoing on the Rust parser, you want to talk to @piegames about that | 16:06:38 |
@acidbong:envs.net | port/rewrite the parser in Rust
not Lix, that's Tvix and Snix folks
| 16:06:40 |
@acidbong:envs.net | welp, Lix isn't planning to use Rust as much as those do | 16:07:01 |
K900 | Lix is definitely planning it | 16:07:14 |
daslixou | well I've read the zulip discussion | 16:07:25 |
K900 | And one of the major blockers towards this has been recently fixed | 16:07:26 |
daslixou | well I've read skimmed over the zulip discussion | 16:07:43 |
@acidbong:envs.net | ah, so they also want to get rid of the eval-build separation? | 16:08:03 |