Their "Appendix: Memory Safe Languages" lists: C#, Go, Java, Python, Rust & Swift
Why is Python listed there and not other languages like Ruby, Javascript or Perl?
I would bet it's more unsafe to use Perl than C, on average.
The Case for Memory Safe Roadmaps
61–70 of 427 posts
Re: The Case for Memory Safe Roadmaps
#62Confused about Python in particular considering a lot of powerful and common dependencies in the ecosystem starting out from numpy and friends all have C/++ components to them for performance improvements. Surely this is a vector to be considered?
Re: The Case for Memory Safe Roadmaps
#63Re: The Case for Memory Safe Roadmaps
#64[flagged]
The NSA’s charter includes both offense and defense: if only American companies choose to do things securely, the NSA gets a double win for free here.
Re: The Case for Memory Safe Roadmaps
#65Isn't C++ with RAII reasonably safe? I tried to learn/like Rust but it's against how I use to think.
If no friendlier safe high speed programming language appears, I rather use C/C++ and trade safety for friendliness.
Re: The Case for Memory Safe Roadmaps
#66I'm cynically thinking "because they can now target the runtimes instead, and get far more value from their exploits".
Re: The Case for Memory Safe Roadmaps
#67At least my usecase has C completely disconnected from the internet. I have no idea how this is going to work at the OS level.
Crossing an air gap hasn't stopped a determined attacker in the past: https://en.m.wikipedia.org/wiki/Stuxnet
Let's be real. Creating an air gap hasn't stopped a very few, unlimited resource, APTs. Don't let perfect be the enemy of good enough.
Re: The Case for Memory Safe Roadmaps
#68I advise training programmers instead of throwing them in front of a screen without any training. Companies these days provides no training at all. When I was hired over 40 years ago, I spent plenty of time being trained for my first 3 months. Now, nothing, and you if you want to train a new person, you do it on your own time.
absolutely correct, in fact now some new hires are expected to do a few git-commit the first day(looking at you, Meta).
no wonder so many bugs here and there.
Re: The Case for Memory Safe Roadmaps
#69I advise training programmers instead of throwing them in front of a screen without any training. Companies these days provides no training at all. When I was hired over 40 years ago, I spent plenty of time being trained for my first 3 months. Now, nothing, and you if you want to train a new person, you do it on your own time.
Startups are likely to fail, big tech is likely to fire the developer (or they quit), and poorly run companies just don't know how to train. End result is it just doesn't happen much anymore.
Re: The Case for Memory Safe Roadmaps
#70Earlier quoted context omitted.
Really, the only memory unsafe languages still in use are C and C++. If it weren't for the behemoth of legacy code we'd really have this problem more-or-less licked. Unfortunately, that behemoth is still rampaging across the landscape. "Rewrite it in Rust" gets a bit of pushback, perhaps even justified, but at this point in time I'll take anything that just reduces that behemoth in size. The journey of a thousand mil…
>Really, the only memory unsafe languages still in use are C and C++. Ada, Fortran, assembly?
Isn't Ada memory-safe?