Linux

Blazingly fast 🚀

Organisations

Suits and shit.

Like 65534 times.

So close to full 16-bit max. So close...

Aviation, Health, Space and Car industry have only 3 certified languages that they use. Ada, C and C++. Ada is dying because there are way less young engineers who want to invest their future learning it. Then there is C and C++ but they dont offer memory safety and its really hard to master and its really hard and long (thats what she said) to certify the code when being audited for safety by a tier company.

Rust solves by default (no need to review) like 2/3 of the standard requirements those industries have and are that found in C and C++. Rust will soon be approved in this group by the car industry.

Im not a rust fan, but I have 3 things to say about rust.

• Its fun to program like C++ having the peace of mind knowing the compiler is there helping.
• You dont feel like youre defusing a bomb like when writing C.
• Even though its a fun language to write, its also really hard to master, itd say 2 years to be really proficient with it. There is just so much knowledge.

I wonder how many folks are just refusing to use Rust to spite the Rust Evangelism Strike Team.

I hate it when people talk about new technologies 🤬

unattended-upgrades and forget about it

Of course a good developer can avoid these problems for the most part. The point is that we want the bad developers to be forced to do things a safe way by default.

But this isn’t one of them

This is a use-after-free, which should be impossible in safe Rust due to the borrow checker. The only way for this to happen would be incorrect unsafe code (still possible, but dramatically reduced code surface to worry about) or a compiler bug. To allocate heap space in safe Rust, you have to use types provided by the language like Box, Rc, Vec, etc. To free that space (in Rust terminology, dropping it by using drop() or letting it go out of scope) you must be the owner of it and there may be current borrows (i.e. no references may exist). Once the variable is droped, the variable is dead so accessing it is a compiler error, and the compiler/std handles freeing the memory.

There's some extra semantics to some of that but that's pretty much it. These kind of memory bugs are basically Rust's raison d'etre - it's been carefully designed to make most memory bugs impossible without using unsafe. If you'd like more information I'd be happy to provide!

Assuming the bootloader is unlockable