IRC channel logs

<jab`>azert thanks for the comments!

<Gooberpatrol66>azert: thanks, I was interested in hearing about the considerations of MIG language bindings

<Gooberpatrol66>azert: so do you think MIG can't be made much more language-agnostic than it is now?

<azert>Gooberpatrol66: yes I really meant that mig can be ported to other languages, user.c and server.c are just files filled with printf

<azert>the easiest way to port MIG to rust is to just reimplement those file, and a flag to chose whichever language to generate

<nikolar>So is Hurd going through the "rewrite it in rust" meme

<Arsen>there's no complete enough GNU rust compiler yet, so I doubt it; the above seems to pertain rather to language binding/writing programs

<Gooberpatrol66>i think it'd be good if there were guile bindings, given that's supposed to be the gnu extension language

<azert>For userspace you don’t really need mig, rust software can just target the libc, the GNU libc specifically

<azert>What I really liked about the aarch64 port, is that the heterogeneity of arm hardware support meant that moving the drivers to userspace is a much bigger win

<Gooberpatrol66>man i wish i had more time to work on hurd

<azert>Same

<Gooberpatrol66>linux has been a buggy mess for years and it slowly gets worse with each release

<Gooberpatrol66>each time I DC, it's due to a graphics driver crash

<azert>Exactly, think about the Linux graphics stack, it’s an abomination bigger then the kernel itself

<azert>It would make so much sense to have user space drivers for that

<azert>In a way.. Xorg was just that

<Gooberpatrol66>didn't the kernel DRM stuff used to be done in userspace

<Gooberpatrol66>so the kernel's absorbing userspace

<nikolar>I mean most of the Linux graphics stack is already in userspace

<nikolar>Most of the kernel stuff is just shuffling commands between the GPU and mesa drivers

IRC channel logs

2024-09-22.log