Time to make C the COBOL of this century
-
Unsafe rust has proven that it can be an effective alternative here, ideal especially when the consumers are also rust.
Chicken and egg problem strikes again
-
So the solution is to take away any agency the developer may have over how their application allocates memory?
Have you heard of the
unsafeblock in rust? -
Serious question: How can a programming language be more or less secure than another? I am just a hobbiest, not a professional, so I am genuinely curious.
It's about memory management.
In programming terms: allocated memory has to have the data in it that you expect in order for your program to work. The unsafe languages do it by manually ensuring it's good and doing so mostly at runtime, or just assume the data is valid and write code that looks valid and have somebody check it before the program runs, or do a mix thereof. In all cases, it require a lot of human intervention and because humans are fallible with different skill levels, this fail quite often.
Safe languages are either built on top of unsafe languages that are battle tested and do lots of runtime checks behind the scenes (interpreted languages like python, ruby, javascript, etc.). Then there are languages that check actions at compile time like Rust. They tell you that the memory you're trying to access can be modified by another part of the code, which might make unexpected changes and that in order to access it, certain conditions have to be met.
In laymans terms: imagine you work at a storage facility (memory) and have to store and retrieve packages. To know where to store and retrieve them, you have a piece of paper with the aisle, shelf, and rack and position on the rack. That's your pointer. To store something, you have to make space on a rack and put the item there, write down the name of the item (variable) and location on a piece of paper (memory address), and keep it on you.
Imagine keeping all of that in order. You have to make sure you don't write down the wrong location (off by one error), remove a piece of paper then it's not valid anymore (dangling reference), remove a piece of paper without removing the item (memory leak), add a piece of paper pointing to something without actually checking what you expect to be there is there and then retrieve it later, and so many other things.
Those are the things unsafe languages allow you to do.Safe languages either enforce that before doing certain things, you check stuff (runtime checks) or that before you even start doing anything, you plan how you would do, and that plan is checked.
The crazy storage facilities are what most of our world runs on at the moment and there a whole lot of people who love it because it's simple and they know it. "Just tell the intern to get that box there, I made sure it'll be fine. Trust me, I've been doing it this way for years." meanwhile somebody gets the wrong medicine because a piece of paper said another one was supposed to be on the shelf. There are a bunch of people who have thought about ways to improve it, implemented, tested it, and are using it to manage their storage facilities.
-
This post did not contain any content.
I mean it's never going to go away, because there has to be something to bootstrap all these newer languages from.
https://en.m.wikipedia.org/wiki/Bootstrapping_(compilers)
I absolutely agree that most normal programmers need to move away from C but it's not going to go away anytime soon
-
These tech images are getting pretty ridiculous. What even is this thumbnail?
Getting?
-
This post did not contain any content.
We’ve already seen a few crotchety old timers who don’t want to add rust to the Linux kernel.
At some point, a complete rewrite of the kernel in a memory safe language would be prudent. Unfortunately, the dinosaurs will have to go extinct before that can happen.
-
We’ve already seen a few crotchety old timers who don’t want to add rust to the Linux kernel.
At some point, a complete rewrite of the kernel in a memory safe language would be prudent. Unfortunately, the dinosaurs will have to go extinct before that can happen.
Literally no one is stopping you
-
Literally no one is stopping you
Just those crotchety old timers who currently gatekeep the code base.
-
These tech images are getting pretty ridiculous. What even is this thumbnail?
It's how everyone who's anyone does code reviews!
-
Just those crotchety old timers who currently gatekeep the code base.
That doesn't prevent you from forking it.
-
That doesn't prevent you from forking it.
The Linux kernel is a few hundred million lines of code, probably.
It does need to slowly be moved into a memory safe language. -
System shared this topic
