▲ -3 ▼ Time to make C the COBOL of this century (www.theregister.com) submitted 2 years ago by cm0002@lemmy.world to c/programming@programming.dev 36 comments fedilink hide all child comments
[–] bamboo@lemm.ee 7 points 2 years ago (1 child) If it ain't broken, don't fix it. That’s the thing, it is broken and there is a fix desperately needed. C lacks memory safety, which is responsible for many, many security vulnerabilities. And they’re entirely avoidable. permalink fedilink source parent hideshow 2 child comments replies: [–] deathmetal27@lemmy.world -5 points 2 years ago (2 children) So the solution is to take away any agency the developer may have over how their application allocates memory? permalink fedilink source parent hideshow 4 child comments replies: [–] bamboo@lemm.ee 11 points 2 years ago Remove the need to, yes. Remove the ability to? No, and rust doesn’t prevent you from doing that, it just makes you mark it unsafe so that way if you fuck up and cause a memory error, the root cause can be narrowed down to a tiny fragment of the code base. permalink fedilink source parent [–] onlinepersona@programming.dev 2 points 2 years ago Have you heard of the unsafe block in rust? Anti Commercial-AI license permalink fedilink source parent
[–] deathmetal27@lemmy.world -5 points 2 years ago (2 children) So the solution is to take away any agency the developer may have over how their application allocates memory? permalink fedilink source parent hideshow 4 child comments replies: [–] bamboo@lemm.ee 11 points 2 years ago Remove the need to, yes. Remove the ability to? No, and rust doesn’t prevent you from doing that, it just makes you mark it unsafe so that way if you fuck up and cause a memory error, the root cause can be narrowed down to a tiny fragment of the code base. permalink fedilink source parent [–] onlinepersona@programming.dev 2 points 2 years ago Have you heard of the unsafe block in rust? Anti Commercial-AI license permalink fedilink source parent
[–] bamboo@lemm.ee 11 points 2 years ago Remove the need to, yes. Remove the ability to? No, and rust doesn’t prevent you from doing that, it just makes you mark it unsafe so that way if you fuck up and cause a memory error, the root cause can be narrowed down to a tiny fragment of the code base. permalink fedilink source parent
[–] onlinepersona@programming.dev 2 points 2 years ago Have you heard of the unsafe block in rust? Anti Commercial-AI license permalink fedilink source parent