Debian, Rust, and librsvg

Posted Nov 14, 2018 15:32 UTC (Wed) by glaubitz (subscriber, #96452)
In reply to: Debian, Rust, and librsvg by mathstuf
Parent article: Debian, Rust, and librsvg

> One big difference is that systemd is *never* going to be ported (as a project, not necessarily as an API). There's nothing saying that Rust won't support those other platforms other than a lack of resources.

I agree. However, the discussion on debian-devel was started with the background of the status quo where Rust has currently limited portability.

Don't get me wrong: I think that Rust is a great project and language, I have even contributed some patches myself to help with the portability issues. I have definitely no problem with people re-writing their code in Rust. I just wished more Rust developers would take portability more seriously. It would really be great if we could use Rust everywhere where gcc works so that no upstream project would have to worry about excluding certain users when re-writing their code in Rust.

Debian, Rust, and librsvg

Posted Nov 16, 2018 8:35 UTC (Fri) by NickeZ (guest, #100097) [Link]

> I just wished more Rust developers would take portability more seriously.

If this really is what you want your approach is clumsy at best. I'm afraid complaining like this will only get you enemies and developers even less interested in your niche. Instead, you could have written inspiring blog posts / held talks on meetups about how you fixed several archs in the compiler.

Debian, Rust, and librsvg

Posted Nov 16, 2018 12:51 UTC (Fri) by hsivonen (subscriber, #91034) [Link]

I think it is unproductive and misleading to suggest that portability needs to be taken more seriously if the set of targets isn't exactly the same as for GCC and when the missing targets are architectures that have been out of chip production for years.