Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Probably the Rust code will be drivers for devices that are not compatible with non-rust supported architectures anyway.


If the drivers are for PCI or USB devices, then they would have probably worked for those unsupported architectures "for free" if they were written in C.


By the time these kind of drivers are being written in Rust, the gcc support will be there anyway.


Also true, but there's a precedent for Rust developers & shipping their changes without regard for what's being deprecated. [1]

[1]: like when PyPI cryptography first switched to Rust and broke ansible/openwrt/etc.


The Linux kernel takes backwards compatibility much more seriously than your typical Python package.


The Linux kernel community and Rust community still aren't on the same page on things yet, as you'll learn by reading lwn regularly.

We're just not there yet.


Seems like Linus and Greg and a bunch of people who oversee technical decisions on the Linux kernel are on board though?


And they can back-out/revert if they decide to as well


ansible... btw. ansible breaks basically tons of stuff every release, so no matter if the pypi crytography broke ansible. ansible is already broke. heck they renamed their package in the most stupid way ever...




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: