6 comments
@cwebber i don't think i understand your point. currently it's straightforward, using standard tooling, to make a rust dynamic linked shared library and export C headers for it. a lot of mozilla projects are doing this @haskal yes, you can do it. but you aren't having conversations with the same people in the Rust community as I have, clearly. (Notably all the annoying Rust developers are cis dudes, and most of the cool ones are trans girls, who don't typically share this same attitude. Despite the fediverse's reality distortion field, that's not the majority of Rust devs in the wild) @cwebber i mean i could write an imagemagick in rust today and export even fully imagemagick-compatible C bindings and have a drop in replacement shared library |
@cholling @haskal I do think it's annoying that C has become the lingua franca. Rust could provide an alternative, that would be a good initiative on its part. It would still require dynamic linking. Support for the C ABI isn't the primary thing I'm advocating for, it's pointing out that dynamic linking is where C has had the most success.