The US government wants devs to stop using C and C++
The US government wants devs to stop using C and C++
Does anyone want to tell Linus Torvalds? No? I didn't think so
The US government has more pressing issues I think.
Maybe it can shut the fuck up an let me do my job in contrast to its judicial branch.
What if I told you the judicial branch is doing its job because it was always evil to begin with?
I would say you’re right
I don't get why we're taking a swing at Linus here. The article only mentions him in relation to the rust for Linux project being slow going. But, it IS going and the US government has only stated that "you need a plan to move to a memory safe language by 2025 or you might be liable if something bad happens as a result of the classics (use after free/double free/buffer overflow/etc.)" but I don't think Linux would count it's free software and it does have a plan.
Why the swipe at Linus? He's been supportive of rust in the Linux kernel.
they don't swipe him at all. I don't know why his picture is there
because that makes people click
Maybe read the article...
Imagine if there was a hack so bad that it caused everyone to become unable to develop in C and C++.
Classic "let's just make the cure worse than the disease" mindset among security enthusiasts.
Imagine if there was a hack so bad that it caused everyone to become unable to develop in C and C++.
Well, there is one that will imply you can only develop using anything that you have bootstrapped yourself, using hardware that you have designed and manufactured yourself, using tools that you have designed and manufactured yourself, using tools that you have designed and manufactured yourself ...
... with your own bare hands.
If only it were that easy to snap your fingers and magically transform your code base from C to Rust. Spoiler alert: It's not.
How utterly disingenuous. That's not what the CISA recommendation says, at all.
yeah No.
well, i'm glad the US government is at least aware what C and C++ are!
"Oh, I thought I was coding in Python. Oops!"
Continues coding in C++
Jython's your Python
The comment thread in that article is interesting. Grep for Ada.
The US government hates anything that can perform math too fast.
As someone who learned Ada for a defense job years ago, I've been wondering how long it was going to take until I saw others comparing Rust to it, both in the sense of the language "safety" goals and the USG pushing for it.
While the rust compiler is leagues better than any Ada compiler I ever had the misfortune of dealing with, the day to day pain that Rust incurs will probably always be a thorn in it's side
Need more carrot
My friend from university sends me his Rust code snippets sometimes. Ngl it looks like a pretty cool language.
There was also that tldr reimplemention in Rust that is a gatrillion times faster than the original.
I really want to give it a try but I have executive dysfunction and don't have any ideas of what I could use it for.
The main issue I have with rust is the lack of a rust abi for shared libraries, which makes big dependencies shitty to work with. Another is a lot of the big, nearly ubiquitous libraries don't have great documentation, what's getting put up on crates.io is insufficient to quickly get an understanding of the library. It'd also be nice if the error messages coming out of rust analyzer were as verbose as what the compiler will give you. Other than that it's a really interesting language with a lot of great ideas. The iterator paradigm is really convenient, and the way enums work leads to really expressive code.
As someone that have worked in software for 30 years, and deplying complicated software, shared libraries is a misstake. You think you get the benefit of size and easy security upgrades, but due to deployment hell you end up using docker and now your deployment actually added a whole OS in size and you need to do security upgrades for this OS instead of just your application. I use rust for some software now, and I build it with musl, and is struck by how small things get in relation to the regular deployment, and it feels like magic that I no longer get glibc incompatibility issues.
Documentation is generally considered one of the stronger points of rust libraries. Crates.io is not a documentation site you want https://docs.rs/ for that though it is generally linked to on crates.io. A lot of bigger crates also have their own online books for more in depth stuff. It is not that common to find a larger crate with bad documentation.
fn executive() {}
I thought the US Government bought a lot of software in Ada, so I hope they continue with that.
The comment section mentions that conundrum as well... quite interesting.
To address this concern, CISA recommends that developers transition to memory-safe programming languages such as Rust, Java, C#, Go, Python, and Swift.
If only it were that easy to snap your fingers and magically transform your code base from C to Rust.
guy_butterfly_meme.jpg is this unbiased journalism?
lol ok.
Well now I'm going to have to use it even more.
Because they want to replace them with more corporate-controlled languages.
Just add
@safe:after yourmoduledeclaration, and you'll be safe by default if you don't want to wait until D3.Also, unlike in Rust, you can opt-out from RAII with
int foo = void;, although it primarily has a performance advantage with arrays, not singleton variables (might be also useful for aquiring an RNG seed in a dumb way).Jep, you got em, it's all a conspiracy so they poison our mind with the evil tongues and make us corpo slaves with the help of Rust.
I don't see python on your image :)
Too bad! Stay in your lane, pinche government!
Eventually, painfully, slowly, we'll move to memory-safe languages. It really is a good idea. Personally, though, I don't expect it to happen this decade. In the 2030s? Yes, 2020s? No.
This. Unless the government starts introducing fines or financial incentives (like fines) to force the use of memory-safe languages, ain't nothing gonna happen.
Ok, and what do you think the memory managers were written in?
Who cares? Just like most things your average programmer relies on, they are written by smarter or at least more specialised people to make your job easier. They have learned to write memory-safe code so you don't have to.
More specialized is critical.
You have to understand your domain, what your goal is, how much time and money you have, etc.
God, this old argument... Careful, it's an antique.
The idea is to minimize memory management and have people who are experts on it deal with it.
AFAIK, the first one was written in LISP.
The one most people push around here was written in Rust. It's a really great language to write memory managers anyway.
I don't think those are the problem, but rather how they are used. And in case of managed languages like C#, it's almost impossible to shoot yourself in the foot when it comes to memory management. You still can, if you really wish, but you have to be very explicit in that. 🤷♂️
If it’s broke, don’t fix it amiright?!
Don't worry bud, I'll upvote you. Not everyone is afraid of pointers.