C#, Go, Java, Python, Rust, and Swift
this post was submitted on 13 Dec 2023
79 points (98.8% liked)
Programming
17437 readers
238 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities [email protected]
founded 1 year ago
MODERATORS
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
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.
Sorry, are you saying the NSA's information sheet shouldn't have mentioned specific languages? Why not?
If you aren't getting seg faults, are you really living?
Stop using C/C++
Spread the word far and wide.
Obscure hardware still gotta be supported somehow
What are you implying here?
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)
The NSA said this? Looks like it's just going to be assembly for me from here on out. /s, ofc
fedjacketing rust devs on the funny shaped ursine website
Yes, they've been saying it for a year, at this point they're repeating themselves: https://www.malwarebytes.com/blog/news/2022/11/nsa-guidance-on-how-to-avoid-software-memory-safety-issues/amp
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.