145
C++ creator rebuts White House warning
(www.infoworld.com)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 19 Mar 2024
145 points (92.9% liked)
Programming
16210 readers
136 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 !webdev@programming.dev
founded 1 year ago
MODERATORS
I'd probably say it depends but I'm no Rust expert and I have no direct experience with C (though quite familiar with C++).
Basically I'd expect writing C to be easy, but not safe. IE you can quickly and easily write C that compiles but has runtime issues. Rust for the most part will catch everything but logic issues during/before compilation meaning once the program runs you'll have very high confidence in it's runtime behavior leading to time spent "fighting the compiler" instead of figuring out wtf is going wrong at runtime.
I think primarily I don't really care to argue about if it's harder to write or not since it doesn't really matter. I think the pros Rust provides are worth all it's cons
So what's "easy" about it then? Just getting something to compile? That's not a very good measure of "easyness".