| 22 Jan 2026 |
 hexa | https://youtu.be/t6-cCh9bTG4?si=eH4hZE-9YZaGuCO-&t=14 | 08:40:43 |
 m | In reply to @commentator2.0:elia.garden
https://lix.dev/blog/introducing-lix/
Ohno #molotov | 15:21:38 |
 Acid Bong | In reply to @commentator2.0:elia.garden
https://lix.dev/blog/introducing-lix/
Ohno i guess Lix isn't registered yet | 16:09:43 |
| Acid Bong | (the bane) | 16:09:52 |
| Acid Bong | *name | 16:09:58 |
|  Lotte (it/its)/Cinny (she/her) θΔ& changed their profile picture. | 16:47:31 |
 antifuchs | pretty sure there are witches working on the lix project that could arrange for a bane | 17:13:09 |
|  pentane changed their profile picture. | 22:21:03 |
| 23 Jan 2026 |
|  @io:meat.computer left the room. | 00:52:51 |
| 25 Jan 2026 |
 kfiz | Is this currently supported by lix? https://nix.dev/manual/nix/2.22/command-ref/new-cli/nix3-shell#use-as-a--interpreter | 02:55:29 |
| 23 Jan 2026 |
 niko ⚡️ | Does Lix expose any probes for profiling, especially when it comes to eval? | 11:51:38 |
 piegames | What do you mean with probes? If you want to profile your Nix code then it has performance counters you can print with some flags (IIRC), when it comes to profiling eval itself then perf and callgrind it is | 12:44:10 |
 thubrecht | NIX_SHOW_STATS=1 is the env variable that makes it print the counters | 12:54:39 |
|  nea joined the room. | 13:05:52 |
 raitobezarius | we have USDT probes for HTTP transfers | 15:24:01 |
| raitobezarius | i want to introduce more probes, like, significantly more | 15:24:09 |
| raitobezarius | so that it's possible to write an eBPF profiler based on them for eval | 15:24:18 |
