@cjd @david @TheMadPirate @p @ins0mniak
What do you mean by embedded?
IoT. The fact that OpenWRT ships python in a system made to fit in a few megabytes already doesn't bode that well. And for the kernel, I don't see it seeping beyond the driver interface. The core functionality of the kernel needs to run on systems that Rust doesn't officialy support even though it's LLVM. Not to mention that hardware vendors writing drivers for their SoCs in Rust is probably only someone's dream right now. Fun fact: Rust is already sort of mandatory to build kernels, because CONFIG_PCI always builds Rust bindings.
What's important is that ABI-wise, Rust is basically C
Rust is NOT C. You can't link a Rust binary to a C binary without specifically defining the interface in Rust. C has no idea about the gillion of types that Rust has and never will.
Side note:
I also hate that this shitpost of a thread has turned into a Rust discussion thread, like they always do when anything is even slightly programming related and barely technical. It's the loli question of the computer world. And I already hate it.