| 27 Dec 2025 |
 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 |
 Acid Bong | ah, so they also want to get rid of the eval-build separation? | 16:08:03 |
| Acid Bong | (or is it not the point?) | 16:08:14 |
| K900 | That is not the point | 16:08:18 |
| K900 | But that is also something we'd like to do at some point | 16:08:26 |
 raitobezarius | we definitely want to fully go to Rust | 16:09:26 |
| raitobezarius | it's just a matter of possibility | 16:09:32 |
| Acid Bong | oh, didn't know that | 16:09:52 |
| daslixou | also - with a bit confusion, I know that nix is seperated into pkgs and os (and lang), is lix primarily a "better" interpreter? or are there also plans/active things on doing something like lixos? (I'm asking because I dislike using systemd) | 16:10:31 |
| K900 | Lix is just an interpreter | 16:11:12 |
| K900 | There is currently no LixOS | 16:11:19 |
| K900 | But given anyone who is involved in something like that happening, there will be more systemd | 16:11:29 |
| K900 | Not less | 16:11:30 |
| K900 | Because in fact systemd good | 16:12:07 |
| K900 | (mostly) | 16:12:13 |
 Spectral (he/him) | I mean if there evet will be something like LixOS then it should probably not be named that to avoid recreating the whole naming headache that nix has | 16:12:50 |
| K900 | It will not be named LixOS no | 16:13:28 |
 Coca | "it's up to you to break generational trauma" | 16:15:25 |
| Acid Bong | at least it's more convenient than Guix being used for both the repo (guixpkgs*), the OS (guixos*) and the tool
(ik the OS is technically called Guix System, but most ppl drop "system") | 16:16:21 |
 piegames | In reply to @k900:0upti.me
There is some work ongoing on the Rust parser, you want to talk to @piegames about that https://git.lix.systems/piegames/lix-parser it has started ✨ | 16:22:27 |
| piegames | Living out of tree while still in the prototype stage | 16:22:48 |
| daslixou | winnow, I see | 16:23:01 |
| piegames | So to set expectations, the timeline for amy of this is "hopefully still in 2026 but no guarantees" | 16:23:17 |
| piegames | * So to set expectations, the timeline for any of this is "hopefully still in 2026 but no guarantees" | 16:23:31 |
| daslixou | Redacted or Malformed Event | 16:23:32 |
| daslixou | time to make a lix account iguess | 16:26:27 |
| daslixou | I have to ask, from where are the whole stateful, bytecode, parserstate and thunk things from? I want to make sense of how they'd be used | 16:36:08 |
 madmccrow | It's more like : I don't like the way to have latest and stable nixpkgs side by side when developing for machines with radically different missions (ie. Gaming desktop, vs backup NAS) .
If you add the fact that the flake layout might require you to have some inputs twice ( like for example if you wanna use Lanzaboote with both stable and latest).
A lockfile by machine would be better by a mile, but I don't know how to do it without splitting my work in multiple repos.
Because I've read that the lix community wasn't satisfied with flakes in it's current state, I would have thought some alternative was being used. | 16:51:34 |
| Acid Bong | then have two Nixpkgs inputs and define hosts from them, there's no problem with that | 16:53:28 |
