2 ms·
> Saying 'you should have rewritten this in rust in order to avoid liability' is not a standard of care that anybody will ever be held to. Why is 'you should n
by staticassertion 10y ago
> Saying 'you should have rewritten this in rust in order to avoid liability' is not a standard of care that anybody will ever be held to.
Why is 'you should not have exposed C code to the internet' an unreasonable basis for care?
I'm not saying your approach is wrong, I think they're not mutually exclusive - your solution would provide incentive to not use C in a technology agnostic way. But at some point isn't it just irresponsible to write critical infrastructure, or code that exposes user information, in a language that has historically been a disaster for security?
- jacquesm 10y ago> Why is 'you should not have exposed C code to the internet' an unreasonable basis for care? Because it does not mesh with reality. There are 100's of millions of lines of C code exposed to the internet in all layers of the stack. So if you start off with a hardcore position like that you virtually ensure that your plan will not be adopted. It's the legacy that is the problem, not the future.