| 13 Mar 2026 |
raitobezarius | There's the performance problems of what SSH was optimized to do (TCP_NODELAY related topics) | 15:13:03 |
raitobezarius | There's the "use libssh if you want to have control over the thing like readiness, etc." but "if you use libssh, you lose all the advanced openssh features" | 15:13:22 |
raitobezarius | Maybe in Rust-land, we can use a proper config parser and have feature parity with openssh but people do depend on the exact details of openssh configs and this limits our ability to do better than an execve of ssh | 15:13:50 |
raitobezarius | (execve of ssh is also not a great way to run a wire remotely) | 15:14:00 |
raitobezarius | So, if we could bring this down to SSH is only used to authorize your mTLS connection, that'd give users the convenience of SSH key distribution/authentication while having a somewhat performant data channel (H2) | 15:14:40 |
flokli | In reply to @raitobezarius:matrix.org i think the biggest annoyance about gRPC is that it mandates HTTP2 on the wire and it's so annoying Hey, it could be worse. Like varlink over the network. | 15:17:42 |
raitobezarius | let's not talk about varlink | 15:17:54 |
flokli | Oh wait | 15:18:02 |
raitobezarius | also varlink is more like a channel for control planes than data planes | 15:18:25 |
raitobezarius | but i want off the gRPC wild ride, the Nix daemon bespoke protocol wild ride, the SSH as a high performance data plane wild ride and the Varlink wild ride please | 15:18:55 |
raitobezarius | (and cap'n'proto is not even perfect, i know) | 15:19:17 |
piegames | I understand. The RPC migration is getting paid for by an NLNet grant, and I'm currently applying to NLNet for a bytecode/libexpr Rust migration grant | 15:23:56 |
piegames | We might be able to do GSOC next year, but this year unfortunately there are not sufficient mentoring capacities | 15:24:24 |
raitobezarius | I don't think Lisanna would need a GSoC student role as they're mentoring ;-) | 15:25:50 |
raitobezarius | I don't know where you are based neither where you are aiming for a job, but the Lix community also has companies surrounding it in EU (mostly), not necessarily to work on Lix but to work with Lix on other topics; I knew in the past there were also US companies hiring in the Lix community as well | 15:27:24 |
raitobezarius | But I understand the strategy | 15:27:33 |
Lisanna | a lot of my background is low level C so honestly even just seeing stuff like conn << var is like "WOW that's so nice and convenient" for me a little bit still ^-^ | 15:27:55 |
Lisanna | East coast US near DC, unable to move because of partner's in-person job (research reactor tech!), so unfortunately I'm mostly limited to remote. Doesn't have to be working directly on Nix or Lix, maintaining nix-based infra or build systems would also be killer | 15:30:37 |
raitobezarius | i heard antithesis is hiring if that's your cup of tea | 15:32:45 |
raitobezarius | i can throw in a referral | 15:32:52 |
Lisanna | I'd be happy working at antithesis | 15:33:14 |
Winter | ;-) | 15:33:15 |
Lisanna | they already have a nix supergenius tho so what even are my chances lol | 15:35:04 |
raitobezarius | winter would probably give a more direct referral ig | 15:35:10 |
Winter | We are always strapped for people so the chances aren’t low!
IIRC you already applied in the past, right? (Let’s maybe move to DMs.)
| 15:36:56 |
Winter | and ideally not on Matrix (you know how to reach me) bc i hate this platform too much | 15:38:57 |
| 16 May 2024 |
| zrsk joined the room. | 13:54:49 |
samrose | In reply to @lunaphied:lunaphied.me I think there were a few CLs on the Gerrit but nothing being actively worked The other thing that I could do if it helps is test things and try to find bugs. I did do some C++ work in the past, but may lack the time to do it justice here at least for about 30 days or so | 15:55:29 |
Qyriad | we are not in any rush 🙂 | 17:20:53 |
samrose | Would it help to also test out the existing Lix code and try to find issues/bugs etc? | 17:23:21 |