2 ms·

Your argument is not compelling: you've described the drawback without considering the benefits. What if that prominent maintainer hadn't made the mistake (a m

Your argument is not compelling: you've described the drawback without considering the benefits. What if that prominent maintainer hadn't made the mistake (a mistake attributable to poorly captured design or requirements, but not the implementation). Is there something intrinsic to Rust that would lead them to this error? (no, I think not). > Please don't be like these people! Keep the stable software we have, and maybe write new software in Rust. I say: spend your time how you see fit. I love Open Source software, I love GNU/linux and GNOME. But IMO it's always been about scratching an itch first and commitment to a cause second.

matthewbauer 7y ago
It's certainly up to them if they want to rewrite everything in Rust. I'm just saying the net benefit just does not exist for stable software like librsvg or bzip2. > Is there something intrinsic to Rust that would lead them to this error? (no, I think not). There is nothing intrinsic to Rust that creates this kind of problem, besides it being a different language than the project was originally written in. I'm sure Go, Swift, Haskell, Java, or any other language (with the possible exception of C++) would have similar issues. No other language community is quite as arrogant as the Rust community though.
- pjmlp 7y ago
  To be faire, that is not everywhere. The design team always has nice conversations with me, in spite of my schizophrenic view of C++ vs Rust (like both languages, see some negative issues in both), and there are places with joint community events between C++ and Rust.
- bsder 7y ago
  > I'm just saying the net benefit just does not exist for stable software like librsvg or bzip2. Are you sure? Both of those libraries are, in fact, poster children to be rewritten in Rust as they have to eat untrusted input. If I offered $20 on "I can find a use-after-free or undefined behavior bug somewhere in those libraries" I'm pretty sure nobody would take that bet.

matthewbauer 7y ago

It's certainly up to them if they want to rewrite everything in Rust. I'm just saying the net benefit just does not exist for stable software like librsvg or bzip2. > Is there something intrinsic to Rust that would lead them to this error? (no, I think not). There is nothing intrinsic to Rust that creates this kind of problem, besides it being a different language than the project was originally written in. I'm sure Go, Swift, Haskell, Java, or any other language (with the possible exception of C++) would have similar issues. No other language community is quite as arrogant as the Rust community though.

pjmlp 7y ago
To be faire, that is not everywhere. The design team always has nice conversations with me, in spite of my schizophrenic view of C++ vs Rust (like both languages, see some negative issues in both), and there are places with joint community events between C++ and Rust.
bsder 7y ago
> I'm just saying the net benefit just does not exist for stable software like librsvg or bzip2. Are you sure? Both of those libraries are, in fact, poster children to be rewritten in Rust as they have to eat untrusted input. If I offered $20 on "I can find a use-after-free or undefined behavior bug somewhere in those libraries" I'm pretty sure nobody would take that bet.