/explore
|
You are here 
|
gavinhoward.com | ||
| | | | |
nora.codes
[AI summary] The article explains the concept of 'unsafe' in Rust, clarifying that it allows specific low-level operations while maintaining overall memory safety through the language's type system and safe abstractions. |
|
| | | | | ||
| | | | |
vale.dev
[AI summary] An in-depth technical explanation of Vale's memory safety strategy utilizing generational references, linear style, and regions to optimize performance and ensure safety without garbage collection or reference counting. |
|
| | | | | ||
| | | | |
www.thecodedmessage.com
The NSA recently published a Cybersecurity Information Sheet about the importance of memory safety, where they recommended moving from memory-unsafe programming languages (like C and C++) to memory-safe ones (like Rust). Dr. Bjarne Stroustrup, the original creator of C++, has made some waves with his response. To be honest, I was disappointed. As a current die-hard Rustacean and former die-hard C++ programmer, I have thought (and blogged) quite a bit about the topic of Rust vs C++. |
|
| | | | | ||
| | | | |
nathanchance.dev
Recently, I built a computer for school that I installed Windows 10 Pro on (link to the current specs if you are curious). I was a little bummed about leaving Chrome OS because I was going to lose my local Linux development environment; however, Windows Subsystem for Linux is a thing and it has gotten even better with WSL 2, as it is actually running a Linux kernel so there is full Linux compatibility going forward. |
|
| | | |||
