| 26 Mar 2026 |
 raitobezarius | for me, i'm addict to the performance improvement for sandbox launch lol | 15:52:36 |
 K900 | Thanks for reminding me to actually set log-format in nix.conf lol | 15:56:20 |
 Emma [it/its] | but yeah, hoping for a json RPC interface at some point being built into lix | 15:57:00 |
| raitobezarius | as i said, i doubt we would build this in the lix core ^^ | 15:57:15 |
| raitobezarius | a third party translator is very much doable though | 15:57:22 |
 Zoe Z | Did https://gerrit.lix.systems/c/lix/+/4698 make it into 2.95.0? I don't see it in the release notes. | 16:12:55 |
| raitobezarius | it did! | 16:13:45 |
| Emma [it/its] | interesting change - is it possible to completely disable local builds now? | 16:14:01 |
| raitobezarius | it doesn't have a release note ^^ | 16:14:04 |
| raitobezarius | i think it's better we do not advertise it too much | 16:14:16 |
| raitobezarius | if you test it well and tell us it works well, we can promote it better later | 16:14:30 |
| raitobezarius | it always was possible with max-jobs=0 | 16:14:49 |
| raitobezarius | now we are making it possible to build only preferLocalBuilds=true things | 16:15:01 |
| Emma [it/its] | the change itself as far as i can see explicitly gets rid of max-jobs=0 | 16:15:21 |
| raitobezarius | --max-jobs=0 --extra-local-jobs=0 will restore the old --max-jobs=0 behavior | 16:15:43 |
| Emma [it/its] | ah | 16:16:01 |
| Zoe Z | It does change the the --max-jobs=0 behaviour (even if it's to more closely match the docs) so I think it's possible someone might find it surprising given the absence from the notes. | 16:17:49 |
| raitobezarius | I agree | 16:18:30 |
 zoë (she/her) | okay so wait, the RPC thing mentioned everywhere is both for communicating with the backend but also for the frontend? i thought it was basically a different way to do remote builds (that was better for some technical reason that i don't know about) | 17:09:16 |
| raitobezarius | its scope is quite broad and large | 17:09:40 |
| raitobezarius | but there's basically 3 components or so in Lix I'd say | 17:09:48 |
| raitobezarius | evaluator, store and build | 17:09:56 |
| zoë (she/her) | so basically the endgoal is to have nix mostly be the evaluator/.drv generator, and then everything else is modular? | 17:10:08 |
| raitobezarius | if each of these piece has an RPC interface, that'd be great to build alternative frontends or backends depending on what you focus | 17:10:37 |
| raitobezarius | even the evaluator would be modular | 17:10:43 |
| raitobezarius | we would like .drv to be a impl detail too | 17:10:53 |
| zoë (she/her) | wait so what's left then? if the build is done by rpc to another module, the eval is done by another module, and the orchestration is done by another module? | 17:11:29 |
| raitobezarius | what do you mean by what is left ^^ ? | 17:11:47 |
| zoë (she/her) | what's the core role of Lix if both eval, build and store are modular? | 17:12:34 |
| zoë (she/her) | will it just be "the standard 'nix idea' impl that plays nice"? | 17:12:44 |
