Do you have an example where Rust devs wanted to break backwards compatibility? The complaints I’ve seen were mostly “I don’t want to learn another language, so your Rust stuff will be broken by us”
A quick search and I’m not able to find anything, so either I’m not using the right search terms or I’m completely off the mark and am mixing up my Tovald Rants.
If I mixed that up, I’m so sorry for spreading FUD!
In fairness, “I don’t want to maintain bindings for a language I never intend to use” is a perfectly reasonable position.
The typical answer here is for the language evangelist to implement and maintain the bindings, and accept the responsibility of keeping them in sync with the upstream (or understand that they will be broken for however long it takes for another community member to update them).
Do you have an example where Rust devs wanted to break backwards compatibility? The complaints I’ve seen were mostly “I don’t want to learn another language, so your Rust stuff will be broken by us”
A quick search and I’m not able to find anything, so either I’m not using the right search terms or I’m completely off the mark and am mixing up my Tovald Rants.
If I mixed that up, I’m so sorry for spreading FUD!
There was a rant like that but directed at a specific developer that was pushing a userspace breaking change. It was not related to a Rust.
Thanks! I know I’ve seen more than and I thought a couple had been about Rust, for some reason!
In fairness, “I don’t want to maintain bindings for a language I never intend to use” is a perfectly reasonable position.
The typical answer here is for the language evangelist to implement and maintain the bindings, and accept the responsibility of keeping them in sync with the upstream (or understand that they will be broken for however long it takes for another community member to update them).