Yeah. Although Wayland is NOT modular, as on the compositor taking care of things that probably shouldn’t be controlled by it, and Rust’s compiler doesn’t support every architecture under the sun, unlike C.
“the compositor takes care of things it shouldn’t” said the x11 user while using their display server that also manages printers, and also provides peripheral drivers, and also manages opengl drivers, and also provides a full graphic toolkit, and also provides remote access. And all that while treating multiple monitors like a single big monitor with a single shared refresh rate, and with no support for HDR of trackpad gestures.
Yes, it really is upsetting when the screen compositor manages screen recording and double buffering.
And remember x11 is so modular that the graphic server is part of the driver stack and so must be implemented for every GPU out there.
P.s.: anyone that thinks the Unix philosophy has any value should not touch xorg with a 10 meter pole. It does many things, badly. But sure, it does allow any unprivileged program to read and write to the framebuffer, so be my guest if that’s your thing.
Why would it need to be modular? What kind of modules should even be there?
It can be implemented in multiple ways anyway.
Rust programs are extremely slow when I build them, it really take ages on my machines, but it works just fine.
Yeah. Although Wayland is NOT modular, as on the compositor taking care of things that probably shouldn’t be controlled by it, and Rust’s compiler doesn’t support every architecture under the sun, unlike C.
“the compositor takes care of things it shouldn’t” said the x11 user while using their display server that also manages printers, and also provides peripheral drivers, and also manages opengl drivers, and also provides a full graphic toolkit, and also provides remote access. And all that while treating multiple monitors like a single big monitor with a single shared refresh rate, and with no support for HDR of trackpad gestures. Yes, it really is upsetting when the screen compositor manages screen recording and double buffering. And remember x11 is so modular that the graphic server is part of the driver stack and so must be implemented for every GPU out there.
P.s.: anyone that thinks the Unix philosophy has any value should not touch xorg with a 10 meter pole. It does many things, badly. But sure, it does allow any unprivileged program to read and write to the framebuffer, so be my guest if that’s your thing.
Rust is an ecosystem that works almost, but not quite, entirely unlike C.
If I remember correctly, then C doesn’t support all architectures that rust supports (and vice versa).
Why would it need to be modular? What kind of modules should even be there? It can be implemented in multiple ways anyway. Rust programs are extremely slow when I build them, it really take ages on my machines, but it works just fine.