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 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
If you're looking to write the types of server daemons often written in C, Go is another good choice. It's very C-like in its syntax. It has a lot of the same safety features Rust has but isn't nearly as complex to learn. It also has a huge standard library, so you rarely need to rely on third-party code.
Go isn't too suitable for drivers or kernels or other kinds of system software though. Rust is definitely a better choice for those.
Just because you can, doesn't mean you should. For application code, it's almost always better to use a language with garbage collection, in order to get memory safety without undue ceremony. Yes, some gc-ed languages are slow (Python, Ruby), but others are quite fast (JVM, .NET, Common Lisp, Haskell).
Skill issue. Just write better code
I hope you're joking. This mindset has had terrible consequences, such macho bullshit needs to go.
The Zionazis will find your mistakes before you do. So have the computer check your work as much as possible.
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
If you're looking to write the types of server daemons often written in C, Go is another good choice. It's very C-like in its syntax. It has a lot of the same safety features Rust has but isn't nearly as complex to learn. It also has a huge standard library, so you rarely need to rely on third-party code.
Go isn't too suitable for drivers or kernels or other kinds of system software though. Rust is definitely a better choice for those.
Yeah I've been using Go a lot lately. It's pretty good
skill issue
huh? about the only place I can't use rust is on microcontrollers, and it's kind of a pain in the dick on mobile (just use kotlin lol)
Just because you can, doesn't mean you should. For application code, it's almost always better to use a language with garbage collection, in order to get memory safety without undue ceremony. Yes, some gc-ed languages are slow (Python, Ruby), but others are quite fast (JVM, .NET, Common Lisp, Haskell).
Most rust programmers don't know how to implement a linked list