> If you add new code to a sw project in c or c++ that should be a solid case for negligence when your customers sue for losses.
Sure, as long as you are ok being similarly sued next time you install or use windows, macos, or linux on some box you administer. Those are all written in C. I guess you're OS-less until you write one in something safe. Ditto for web browsers and bootloaders.
Moreover, a significant fraction of JS vulnerabilities are logic errors in the JIT, so even if the JIT itself is memory safe, that doesn't make the resulting code free of vulnerabilities.
> next time you install or use windows, macos, or linux on some box you administer.
I don't administer other people's boxes, I provide them with programs written in safe languages (as a bootable unikernel if they want). If they choose to run them on a buggy OS that's on them.
I didn't mention rust. If you were targeting something that only has a c compiler and it is critical infrastructure, f* could prove correctness and then generate c from that as an ir. A lot of safety crtical stuff uses a DSL to generate c that humans don't touch afterwards.
Ok that is pretty funny. It is the first time anyone has used any of those adjectives about me even in satire. Didn't mention rust though. I like it a lot, but it is just one tool. F*, agda etc all probably have a more fundamental part to play than rust does. Rust is just the one we can use at scale.
Fun fact, there has been some investigation into Rust for Nonstop, but it’s just not feasible. Like a lot of software. I hear they tried to port gcc multiple times and failed too…