This voluntary guidance provides an overview of product security bad practices that are deemed exceptionally risky, particularly for software manufacturers who produce software used in service of critical infrastructure or national critical functions (NCFs).
I'm actually in favor of this. It's a really good idea, and I hope the state uses it for all the important databases they're gonna use to put us in the camps.
Please dont be a hater. Comrade AI might just save lives here.
that seems like it wouldn't work very well except maybe for small programs. the kinds of bugs they're trying to catch and prevent here may need substantial changes to the program's design in order to prevent. Like the borrow checker literally does not exist in C and it is not a thing people thought about when writing asynchronous C code. Maybe the AI will take a shortcut and write a bunch of unsafe rust code, but in that case what's the point?
They figured out some security hole in C++ programs that makes them even worse than we thought
Some contractor bribed them to say this so that they can get contracts porting stuff to Rust
Some contractor dug up new legitimate security holes in C++ programs so they can convince the FBI to say this so they can get contracts porting stuff to Rust
High ranking FBI officials are rust fanboys
I think contractor bribes, but I think that last two are fun.
It's just the obvious thing. C and C++ don't have safeguards against dangerous programming mistakes. Programming languages exist that do. There are to this day still software vulnerabilities being caused by subtly incorrect code that C and C++ require being treated as legitimate.
their reasoning is that rust (and perhaps others) that can be used in place of c or c++ have stronger compile time memory and thread safety checking which are two major sources of bugs and exploit vectors. So it's not like they're infiltrating the language in this case the way they would with crypto.
Right but AI translating of all government code is good. This is what you want, especially if shit goes down. Dont tell your enemy to stop pouring the kool aid.
It's not really a strong point. C++ has its place for graphics programming and gamedev and C has its place for embedded, but Rust would be a better choice for something like a cryptography app to help revolutionaries communicate for example.
You joke, but modern Java is much less bad than it used to be, the JVM is very well optimized, and other JVM languages like Kotlin and Clojure are actually good.
I am mostly joking but rust is quite annoying and is only useful in very specific circumstances. I'm not against encouraging people to use better designed languages than C though
My only real criticisms of rust are aesthetical. I never liked how C++ is full of macros and :: and <> and rust inherits that a bit.
I use Go because of the work I do right now, which is deep in Kubernetes and APIs for which Go is just more convenient. Protobuf and K8S are of course supported by rust and many other languages as well, but in Go it’s simply easy… Go was designed from the bottom up to write APIs basically so it’s good at that. And most, almost all, of the K8S ecosystem uses Go which means I’d need a good reason not to use Go for that since standardization, interoperability, and ecosystem are key concerns.
You can use rust for this too, for sure no problem. But with Go you’re doing all of that pretty much out of the box.
The Go ecosystem in general is a little bit stronger due to higher adoption, although I wouldn't really call that a weakness of rust.
And finally less people use Rust which is another consideration for long term maintenance concerns, but to be fair Go adoption is also low.
I’m never an evangelist for any language. Well, if I could simply write everything in typescript I would to be honest because I think it’s just swell but obviously its not for this use case, and the above are the reasons why I use Go and get my teams to use Go for the use case of services, Kubernetes controllers, and since we want to use Go for those things we then also use Go for other random things like CLIs etc just because it makes sense to limit tech stack sprawl.
also, separate comment, what are you generally building? if you're writing Go because it's network code, you might want to look into Elixir. It's GC but the behavior of BEAM is more soft-RT friendly due to its history in telephony, you might be more at home there
i have not tried it myself but have you taken a look into zig? it looks alot like go but is lower level. i have heard good things about it and it looks nice. of course the ecosystem is quite limited since it's a quite new language
Is CERT code included? I think there is a group working on a secure version of C++ as well. I'm not convinced that shifting experienced programmers to mew less familiar syntax will improve software quality. Improving the language rather than changing to another might be a better approach.
I guess assembly also ought to be avoided since all of the power/flaws of C are extant in it as well.