Interesting comparison of the different choices made in Rust and the upcoming C++26 for code generation. It's fascinating how they managed to have such facilities in Rust while having no introspection. C++ going the opposite direction will have a very different feel both in term of use or of implementation.
Excellent proof of why you don't want to "rewrite it all in Rust". It's important to respect the old code and focus on applying safety practices on the new code. This is also why the upcoming changes to C++ are worth it, it might improve the interoperability factor almost for free.
Despite the drama, Rust is slowly making its way into the kernel.
An interesting endeavor to create you own OS using another language than one of the usual ones.
Interesting analysis. For sure the Rust for Linux drama tells something about the Linux kernel community and its complicated social norms.
Politics in the Linux kernel can indeed be tough. The alternative path proposed to the Rust-for-Linux team is indeed an interesting one, it could bear interesting results quickly.
Need to make a realtime collaboration application? This might come in handy.
It's nice to have a balanced view on the matter. It's not just roses and rainbows. This gives a good overview of the current limitations and where Rust can give most benefits in the kernel.
Ever wondered how this operator is implemented in Rust? It's not that complicated.
Funny read, it has lots of good advice for starting up with Rust.
Nice balanced view on some of Rust characteristics. This is much less naive than some of the "Rust is great" posts out there.
In which case you want one or the other? This is illustrated in the Rust case which has its own struggles, but the question applies more largely in my opinion.
Check out the docs branch for detailed explanations. This exhibits a loop hole in the Rust compiler allowing to break lifetime inference... and from there all the usual guarantees go through the window.
Interesting, I didn't know that user space schedulers were coming to Linux. It opens the door to exciting experiments.
It's hard to argue that the Rust type system isn't superior to the C++ type system... it's definitely nice how it actively prevents data races at compile time.
Indeed, not all security issues are due to memory related problems. It's 20% of the security issues. This is of course massive, but there's still 80% of the security issues coming from wrong authentication, appliances and so on.
If they really commit to it, this means Microsoft will really invest big in Rust. Let's wait and see...
Interesting tricks for having good vector graphic based animations and collision detection.
I like this kind of rabbit holes. This gives a few interesting information on how forking processes behaves on Linux.
Very interesting contribution to the FreeBSD hackers mailing list. Gives quite a good background about Rust, C++ and safety. Debunks a few claims you can easily hear in many places as if they were common knowledge.