If you want it to be 100% bug free, there's really only one choice. Re-write the kernel in Rust. You'll be guaranteed to have no race conditions. It's impossible.
Exactly! This software should be re-written in Rust, ASAP! Any software that's mission critical at all shouldn't be written in anything but. Now that Rust's technology exists, it's almost criminal not to use it.
This is such a good idea. When shell scripts are all written in Rust, Unix will be a safe and secure operating system.
If they used a language like Rust instead of Swift, iOS would be much more immune to these sorts of attack. There would be no side channels.
Rust may have a "higher learning curve" but it also takes a "learning curve" to learn to debug memory errors. I argue that it's actually quicker to learn Rust.
Rust may have a learning curve, but debugging memory errors has an even steeper one.
I think users want safety. And that means Borrow Checkers. It's 2018, no need to have languages that are inherently unsafe.
If you want it to be 100% bug free, there's really only one choice. Re-write the kernel in Rust. You'll be guaranteed to have no race conditions. It's impossible.
Exactly! This software should be re-written in Rust, ASAP! Any software that's mission critical at all shouldn't be written in anything but. Now that Rust's technology exists, it's almost criminal not to use it.
This is such a good idea. When shell scripts are all written in Rust, Unix will be a safe and secure operating system.
If they used a language like Rust instead of Swift, iOS would be much more immune to these sorts of attack. There would be no side channels.
Rust may have a "higher learning curve" but it also takes a "learning curve" to learn to debug memory errors. I argue that it's actually quicker to learn Rust.
Rust may have a learning curve, but debugging memory errors has an even steeper one.
I think users want safety. And that means Borrow Checkers. It's 2018, no need to have languages that are inherently unsafe.