The NSA advises move to memory-safe languages (www.nsa.gov)
from mac@programming.dev to programming@programming.dev on 13 Dec 2023 22:30
https://programming.dev/post/7222317

#programming

threaded - newest

cerement@slrpnk.net on 13 Dec 2023 22:41 next collapse

C#, Go, Java, Python, Rust, and Swift

pkill@programming.dev on 14 Dec 2023 00:39 collapse

so basically anything without manual memory management. I don’t really see a good point in shilling particular names aside from discussions on performance impact of GC vs VM vs ownership

calcopiritus@lemmy.world on 14 Dec 2023 23:25 next collapse

Not really manual memory management. I’d say C++'s memory management is automatic, just not safe.

Yes, a lot of programming languages are memory safe, maybe it would be faster to list memory unsafe popular languages.

BatmanAoD@programming.dev on 15 Dec 2023 21:09 collapse

Sorry, are you saying the NSA’s information sheet shouldn’t have mentioned specific languages? Why not?

[deleted] on 14 Dec 2023 00:48 next collapse

.

Aurenkin@sh.itjust.works on 14 Dec 2023 03:21 next collapse

If you aren’t getting seg faults, are you really living?

onlinepersona@programming.dev on 15 Dec 2023 17:58 next collapse

Stop using C/C++

Spread the word far and wide.

bruhduh@lemmy.world on 15 Dec 2023 21:48 collapse

Obscure hardware still gotta be supported somehow

onlinepersona@programming.dev on 16 Dec 2023 10:15 collapse

What are you implying here?

bruhduh@lemmy.world on 16 Dec 2023 10:31 collapse

That c lang is simplified assembler and it’s not going to leave cause there no better language to support obscure hardware, i mean, nobody gonna write compilers for obscure architectures to rust or c# because everyone have better things to do, but my idea is, there are alot of obscure hardware out there, actively used even now, and i insist that we should not pollute the world but repurpose every tech there is, and c lang have compilers for almost all existing architectures if not all, also there are alot of manuals how to write compilers to c lang so in case you slap some asic together you can make your own compiler and support your hardware, and modern memory safe languages yet to acquire this feature and that is if they plan to do this at all and not abandon obscure hardware (also I agree with you and upvoted your comments but addition was needed)

oscardejarjayes@hexbear.net on 15 Dec 2023 20:57 next collapse

The NSA said this? Looks like it’s just going to be assembly for me from here on out. /s, ofc

Helmic@hexbear.net on 15 Dec 2023 22:46 collapse

fedjacketing rust devs on the funny shaped ursine website

biscuitswalrus@aussie.zone on 15 Dec 2023 22:13 next collapse

Yes, they’ve been saying it for a year, at this point they’re repeating themselves: www.malwarebytes.com/blog/news/2022/11/…/amp

Aboel3z@programming.dev on 16 Dec 2023 18:59 collapse

I find it amazing that so many are clinging on to C++. It must be that sense of accomplishment when you finally succeed, having solved a bunch of problems on the way. C++ has had so many chances now. Many new standards coming out over the last decade. But the language is hardly simpler, just more to learn. See CoreCppGuidelines. This is what the 2 most prominent people of C++ want developers to learn in order to practice “safe” C++. This doesn’t scale. A language needs to be built from the ground up for developers. Rust has taken a whole new concept and tried to solve memory issues directly with the compiler. Other languages are solving other kinds of issues (for differing kinds of use cases). A language should not put such a burden on the developer.