linux

IIRC it even reboots on its own after a power outage. While macOS presents a "Start up automatically after a power failure" option, and it works, the reality is…complicated. Intel Macs require a model-specific hardware register to be set after each reboot: https://web.archive.org/web/20230218203824/http://www.macfre... The analogous setting on Apple Silicon Macs appears to be nonvolatile: https://github.com/AsahiLinux/linux/blob/de1c5a8be0ee99602e4...

https://asahilinux.org/2022/11/tales-of-the-m1-gpu/ > Since this was going to be the first Linux Rust GPU kernel driver, I had a lot of work ahead! Not only did I have to write the driver itself, but I also had to write the Rust abstractions for the Linux DRM graphics subsystem. While Rust can directly call into C functions, doing that doesn’t have any of Rust’s safety guarantees. So in order to use C code safely from Rust, first you have to write wrappers that give you a safe Rust-like API. I ended up writing almost 1500 lines of code just for the abstractions, and coming up with a good and safe design took a lot of thinking and rewriting! Also https://github.com/AsahiLinux/linux/blob/de1c5a8be/drivers/g... where "drm" is https://en.wikipedia.org/wiki/Direct_Rendering_Manager

You're missing on a lot of things Rust (or any language with non-toy types) can provide. Lock ordering, better accessible complex structures, enforcement of enumerated options, rich description of APIs, and many others. Atomic values are usable transparently https://github.com/AsahiLinux/linux/blob/97c628055904a7f2ef1... and multithreaded reference counting is easily enforced https://github.com/AsahiLinux/linux/blob/bd0a1a7d465fcb60685... also issues like type confusion https://www.vicarius.io/vsociety/posts/a-type-confusion-bug-... are less likely if you can easily use tagged unions checked by the compiler. The best Rust can do is enforce a number of invariants which people extremely experienced in writing "trivial C" still miss every day.

From the gpu issue tracker[0]: > For a bit of context -- Google Maps loads images to the GPU at.. inopportune times. While games would typically load their images during a load screen (so slow image loading just means longer loading screens), Google Maps loads when scrolling around I think (so slow image loading means the whole map stutters). I don't think there's a fundamental driver bug we can fix here, but we can make image loading a lot faster which makes the symptoms go away. [0]: https://github.com/AsahiLinux/linux/issues/72#issuecomment-1...