Before we start, have a look at this image. It is from a German book from the early Nineties, and it features some very interesting cover artwork. A knight with a cape and a big bushy mustache rides a friendly green dragon. A castle, a dolphin, and some animals are in the background. Focus on the details; we will return to that image at the end.

Fettblog offers a blend of technical expertise and creative insight, delving into the intricacies of web development, JavaScript, and performance optimization. Through a mix of tutorials, articles, and hands-on experiments, Fettblog demystifies complex topics like web accessibility, browser APIs, and front-end architecture. Whether you're passionate about crafting fast, responsive web experiences or exploring the latest advancements in browser technology, Fettblog provides the knowledge and inspiration to take your web development skills to the next level.

fettblog.eu

This post explores the concept of 'unsafe' code in Rust, clarifying misconceptions about its impact on safety features such as the borrow checker. It explains that while 'unsafe' Rust does not deactivate the borrow checker, it allows developers to perform certain low-level operations such as dereferencing raw pointers and calling unsafe functions. The use of unsafe code requires careful checks and is encouraged to be kept minimal and well-documented. Examples include creating raw pointers and handling them safely, using safe abstractions, and understanding the responsibilities that come with unsafe operations. The importance of tools like Miri for checking unsafe code is also highlighted.

Unsafe for work