0 views collected around this technical thread.
This article explores how Rust’s innovative ownership, borrowing, and type‑driven error handling move memory safety and concurrency checks from runtime to compile time, contrasting its zero‑cost abstractions with C++ and Go, and demonstrating practical code examples that prevent common bugs.
This article thoroughly compares Rust functions and closures, examining their static versus dynamic characteristics, ownership rules, type system implications, performance optimizations, and practical use‑cases, helping developers choose the right abstraction for safety, speed, and flexibility.
This article explains Rust's closure system, detailing how the three traits Fn, FnMut, and FnOnce map to different capture modes and ownership semantics, and provides practical examples, common pitfalls, and performance tips for writing safe and efficient Rust code.
This article explains Rust’s owned `String` type, showing how to create strings, grow and modify them with various methods, and convert between `String` and `str` while highlighting ownership and borrowing concepts essential for safe memory management.
Rust, a modern systems programming language, offers memory safety without a garbage collector, a powerful ownership model, zero‑cost abstractions, robust error handling, and safe concurrency primitives, making it ideal for high‑performance, reliable software development, as demonstrated through detailed examples and explanations.
Mojo, Modular’s new high‑performance Python superset for AI, adds progressive typing, zero‑cost C++‑style abstractions, Rust‑inspired ownership and direct MLIR access while remaining compatible with existing Python libraries, offering faster, memory‑compact code despite still being early‑stage and lacking full Python feature support.
Rust, a compiled, memory‑safe language that enforces ownership and borrowing at compile time, eliminates garbage‑collection overhead, enabling high‑performance front‑end tools like swc and Rome and efficient WebAssembly modules, though its strict rules present a steep learning curve for newcomers.
This article explains why Rust is valuable for modern development, introduces its memory model, ownership, borrowing, lifetimes, and copy semantics, and provides step‑by‑step guidance for building a WebAssembly image‑processing app with Rust, Cargo, wasm‑pack, and Vite.
This article introduces the Rust programming language, explains its design principles such as memory safety, ownership, and zero‑cost abstractions, compares it with C++ and JavaScript, and provides practical advice, code examples, and insights on when and how to start learning Rust.
This article explains Rust's ownership model, detailing how values are owned by variables, released when out of scope, and transferred or accessed through cloning, moving, immutable borrowing, and mutable borrowing, with code examples illustrating each rule and the compiler errors they prevent.
In his July 11 Engineering Leadership Talk, Baidu’s Lu Qi outlines five essential principles—believing in technology, innovating on the shoulders of giants, pursuing engineering excellence, committing to daily learning, and taking ownership—to guide engineers toward excellence and lasting impact.