Imagine you have a box of toys, each toy has a place where it belongs so you always know where to look for it. After you're done playing with it you put it back where you got it from for next time. On top of that you have a helper who will have a little look through the toy box every so often and they will get rid of any toys you don't need anymore, maybe the toys are broken or maybe you just never want to play with them again. This way we can keep the toy box neat and tidy.
Memory safe programming languages have a set of rules for your computer's "toy box", though instead of toys we have data. We always keep it in the same place and when we're done with it we get rid of it (this is called garbage collection). This helps us prevent accidentally letting someone else see our data and also makes finding and using data much easier.
Sometimes the child decides he really wants to play with his toy car next, so he picks it up and puts it on the little shelf meant for setting things down, then he does this 5 more times with other toys. He tells everyone this is the more efficient and optimized way of getting his toys he knows he wants to play with. The helper was told not to clean that shelf until the toy box is closed, which the child knows so he leaves it open. Someone comes along and steals all of the child's toys because he didn't close it.
Just as the healthcare and broadcasting industries grandfathered the internet, C an C++ grandfathered AI. Kids don't usually play with adults because they are too small. But some adults will abduct and kidnap kids because they are small. There is no and will be no safe code because the system is gaming cheating seniors, adults and children. You won't phase out C or C++ because the healthcare and broadcasters won't give up their blind spots. As they say in prison; "in order to be the man you have to beat the man...". The White House has help put a lot of bad parents in jail, but it has also made a lot of healthcare and broadcasters wealthy. The only good code is one that logs and alerts when RF equipment is live while you are viewing sensitive data. Almost zero ransomware and DDoS attacks occur without a hacker bulletin board evangelizing and converting members to safety. Maybe the White House should suggest Bearcats with their list of memory safe languages.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Imagine you have a box of toys, each toy has a place where it belongs so you always know where to look for it. After you're done playing with it you put it back where you got it from for next time. On top of that you have a helper who will have a little look through the toy box every so often and they will get rid of any toys you don't need anymore, maybe the toys are broken or maybe you just never want to play with them again. This way we can keep the toy box neat and tidy.
Memory safe programming languages have a set of rules for your computer's "toy box", though instead of toys we have data. We always keep it in the same place and when we're done with it we get rid of it (this is called garbage collection). This helps us prevent accidentally letting someone else see our data and also makes finding and using data much easier.
Nice one. But it does not explain how Rust is memory safe though. Guess the metaphor would be somewhat more difficult.
Rust bakes in the helper (garbage collector)
Rust very famously does not rely on garbage collection which is different than memory safety.
technically reference counting is garbage collection
Sometimes the child decides he really wants to play with his toy car next, so he picks it up and puts it on the little shelf meant for setting things down, then he does this 5 more times with other toys. He tells everyone this is the more efficient and optimized way of getting his toys he knows he wants to play with. The helper was told not to clean that shelf until the toy box is closed, which the child knows so he leaves it open. Someone comes along and steals all of the child's toys because he didn't close it.
Just as the healthcare and broadcasting industries grandfathered the internet, C an C++ grandfathered AI. Kids don't usually play with adults because they are too small. But some adults will abduct and kidnap kids because they are small. There is no and will be no safe code because the system is gaming cheating seniors, adults and children. You won't phase out C or C++ because the healthcare and broadcasters won't give up their blind spots. As they say in prison; "in order to be the man you have to beat the man...". The White House has help put a lot of bad parents in jail, but it has also made a lot of healthcare and broadcasters wealthy. The only good code is one that logs and alerts when RF equipment is live while you are viewing sensitive data. Almost zero ransomware and DDoS attacks occur without a hacker bulletin board evangelizing and converting members to safety. Maybe the White House should suggest Bearcats with their list of memory safe languages.