Writing a Wayland Compositor in Zig - Isaac Freund

Writing a Wayland Compositor in Zig

this talk is phenomenal thank you. he explains (timestamp: link to this video ) why he didn't go with Rust and it's quite puzzling what he says. I don't know enough about Rust if that's the case. To rephrase: "Rust was an obvious contender but it lacked good support for wlroots. there was a project which attempted to address this but they gave up after 12 months of work and 1000 commits. Rust's strong safety guarantees and memory management conflict with wlroots which assumes a longer lifetime of pointers. If you unplug your monitor with wlroots this pointer receives an event that means the output has disappeared and needs to be validated (see here link ).* This is strange because Rust positions itse…

Congratulations! And welcome Isaac, I loved his Zig+Wayland screencast 1, where he explained very engagingly how Zig is able to embrace and extend a pretty hairy C library and make it more memory safe, without forcing the implementor to rewrite or painfully try to bend it to the strict or idiosyncratic rules of the language, as it may happen with Rust or even Go. I can't wait for 1.0! Or at least until the docs are a bit more accessible... :) 1: link to this video

The author of River has also done some fantastic talks, on Zig ShowTime 1 and at FOSDEM '21 2. 1 "Writing a Wayland Compositor in Zig" - link to this video 2 "Zig: the perfect language for a Wayland Compositor?" - link

Rust does not bind well with C for this reason it can not become a system level programming link However, there is another programming language that does not need bindings. It is called Zig and here it explains how it solves the same problem link to this video

Another Wayland compositor written in Zig is ifreund/river 1. Isaac, the author, gave a talk on choosing C vs Rust vs Zig on Zig SHOWTIME a while back 2 and also has an upcoming talk at FOSDEM 21 3 1 link 2 link to this video 3 link