NSA urges orgs to use memory-safe programming languages
-
C/C++ on the bench, as US snoop HQ puts its trust in Rust, C#, Go, Java, Ruby, Swift
Don't forget!
-
C/C++ on the bench, as US snoop HQ puts its trust in Rust, C#, Go, Java, Ruby, Swift
Don't forget!
The moment those languages give the performance in near hardware applications, I will consider stop using C/C++ As someone here once said: Do not forget that my compiler compiled your compiler.
M.D.V. ;) If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about? Help me to understand what I'm saying, and I'll explain it better to you Rating helpful answers is nice, but saying thanks can be even nicer.
-
C/C++ on the bench, as US snoop HQ puts its trust in Rust, C#, Go, Java, Ruby, Swift
Don't forget!
Unless you have a specific reason to use C/C++, don't. Yes, it's possible to write memory safe programs in these two languages but it is impossible to prove, except in the case where you don't use the dynamic memory features that your code will not have a buffer overrun, use after free, or other memory related errors.