3 ms·
> Well then the problem would be different?! If instead the problem is the problem as I described it, you have an issue! Maybe. Others will have different situ
by gavinhoward 3y ago
> Well then the problem would be different?! If instead the problem is the problem as I described it, you have an issue!
Maybe. Others will have different situations, so no, even if the problem is as you described it, you may have left out some variable that precludes Rust.
> you are refusing to address how any of this might work in a products liability context.
Yes, I did. I said that we need some objective measure, and I gave a few examples. Anything that doesn't measure up gets hit with liability.
> If you want to say software development is so inherently creative, and subjective, it can never have standards, standards which the rest of the world relies upon to build cars and toys and industrial boilers, then good luck with that opinion.
I never said we could not have standards. That is the opposite of what I said.
I said that we should have a fair objective measure as a standard, not "no memory bugs" or "always write in Rust on Tier 1 and 2 platforms."
> Good luck making this argument!
It will actually be easier with time as more Rust projects appear.
But as a taste, I find it illuminating that, despite calls to rewrite SQLite and Curl in Rust, no one making those calls has actually sat down to do it.
And I do have some personal data in that regard. [1]
> Unfortunate for you, products liability is actually about that metric: safety. If you want to forgo better practices, languages, etc., that's fine. Because products liability law could never simply mandate Rust. You must only be reasonable in your decision making process.
Yes, I agree.
But if we choose the wrong standard, then products liability law will effectively mandate Rust, and that would not be good.
And "safety" is not just about memory safety; it's about that and everything else. Rust is not a valid excuse to forget everything else.
[1]: https://gavinhoward.com/2023/12/am-i-a-good-c-programmer/ https://gavinhoward.com/2023/12/am-i-a-good-c-programmer/