- cross-posted to:
- technology@lemmy.world
- c_lang@programming.dev
- cross-posted to:
- technology@lemmy.world
- c_lang@programming.dev
Biden administration calls for developers to embrace memory-safe programing languages and move away from those that cause buffer overflows and other memory access vulnerabilities.
Why? What’s wrong with safe, managed and fast languages?
Java’s runtime has had a large number of CVEs in the last few years, so that’s probably a decent reason to be concerned.
Yep but:
it’s one runtime, so patching a CVE patches it for all programs (vs patching each and every program individually)
graalvm is taking care of enabling java to run on java
Nothing…
Only that descrition doesn’t include Java
Nothing really, the JVM has a pretty troubled history that would really make me hesitate to call it “safe”. It was originally built before anyone gave much thought to security and that fact plauges it to the present day.
and how much of this troubled history is linked to Java Applets/native browsers extensions, and how much of it is relevant today?
Written in C++
There’s a difference between writing code on a well-tested and broadly used platform implemented in C++ vs. writing new C++.