I don’t think those are the problem, but rather how they are used. And in case of managed languages like C#, it’s almost impossible to shoot yourself in the foot when it comes to memory management. You still can, if you really wish, but you have to be very explicit in that. 🤷♂️
Who cares? Just like most things your average programmer relies on, they are written by smarter or at least more specialised people to make your job easier. They have learned to write memory-safe code so you don’t have to.
Ok, and what do you think the memory managers were written in?
I don’t think those are the problem, but rather how they are used. And in case of managed languages like C#, it’s almost impossible to shoot yourself in the foot when it comes to memory management. You still can, if you really wish, but you have to be very explicit in that. 🤷♂️
God, this old argument… Careful, it’s an antique.
The idea is to minimize memory management and have people who are experts on it deal with it.
AFAIK, the first one was written in LISP.
The one most people push around here was written in Rust. It’s a really great language to write memory managers anyway.
Don’t worry bud, I’ll upvote you. Not everyone is afraid of pointers.
If it’s broke, don’t fix it amiright?!
Who cares? Just like most things your average programmer relies on, they are written by smarter or at least more specialised people to make your job easier. They have learned to write memory-safe code so you don’t have to.
More specialized is critical.
You have to understand your domain, what your goal is, how much time and money you have, etc.