The Goose Programming Language(aardappel.github.io)
155 points by andsoitis | 54 comments
Homepage for Goose, a memory-safe systems programming language with no heap, garbage collector, or lifetime annotations that compiles to C.
27 stories tagged memory-safety, newest first.
155 points by andsoitis | 54 comments
Homepage for Goose, a memory-safe systems programming language with no heap, garbage collector, or lifetime annotations that compiles to C.
268 points by stmonty | 94 comments
Richard Feldman's blog post benchmarking roc-deflate, a pure Roc DEFLATE library, against C's libdeflate, finding it under 10% slower, and describing Roc-specific optimizations.
35 points by jfecher | 2 comments
A blog post from the Ante programming language project describing a borrow-checking approach that allows zero-cost cyclic shared mutability.
104 points by verdagon | 10 comments
Blog post by Evan Ovadia explaining a borrow checker for the Vale language that analyzes functions by walking them backwards to check memory safety.
6 points by embedding-shape | 2 comments
A blog post by a C programmer arguing that Rust's rapid adoption is dangerous, citing corporate control of the Rust Foundation and social hype.
157 points by verdagon | 84 comments
Blog post by Evan Ovadia describing Valen's new flexible borrow checker, where references track the paths they point to, as an alternative to Rust-style borrowing.
54 points by ravenical | 3 comments
Blog post by Sergey Davidoff on making SIMD abstractions in Rust safe internally, avoiding unsafe raw intrinsics.
115 points by signa11 | 110 comments
LWN article covering Martin Uecker's Kernel Recipes talk on undefined behavior in C and whether C can become a memory-safe language.
56 points by computerbuster | 18 comments
Blog post from Halide Compression introducing wpd, a faster, memory-safe WebP image decoder.
90 points by segfaultbuserr | 38 comments
A USENIX ;login: Online article from July 2024 arguing that data-only attacks, which corrupt program data rather than control flow, are easier to carry out than commonly believed.
459 points by lycopodiopsida | 598 comments
Personal blog post arguing that nobody can write correct C or C++ because nearly all code triggers undefined behavior, and that the languages are outdated.
412 points by ndiddy | 285 comments
GitHub issue on the oven-sh/bun repository reporting that Bun's Rust codebase fails Miri checks and permits undefined behavior in safe Rust.
620 points by lwhsiao | 333 comments
A corrode.dev blog post by Matthias Endler about classes of bugs that Rust's compiler and type system do not prevent.
1226 points by adius | 680 comments
Ladybird browser project blog post announcing it will rewrite parts of the browser in Rust instead of C++, after previously exploring Swift, with AI assistance.
331 points by pizlonator | 133 comments
A Fil-C documentation page explaining how memory safety and Linux sandboxing (seccomp) are orthogonal and how Fil-C supports sandboxes.
356 points by abraham | 276 comments
Google Security Blog post by Jeff Vander Stoep on how Rust adoption in Android improves memory safety and development velocity.
340 points by transpute | 219 comments
Daniel J. Bernstein's notes on using the memory-safe C/C++ compiler Fil-C, including install scripts, timings, and compatibility observations on Debian 13.
364 points by rkta | 632 comments
Debian mailing list post by Julian Andres Klode announcing APT will add hard Rust dependencies no earlier than May 2026, asking ports without Rust toolchains to add one or sunset.
456 points by circuit | 212 comments
Apple Security Engineering and Architecture blog post introducing Memory Integrity Enforcement, a memory safety protection system for Apple devices.
556 points by pizlonator | 255 comments
Documentation page describing FUGC, Fil-C's parallel concurrent on-the-fly non-moving Dijkstra garbage collector for memory-safe C/C++.
432 points by tavianator | 421 comments
Blog post by Ralf Jung arguing that memory safety cannot be separated from thread safety, using a Go data race example, and that the real goal is absence of undefined behavior.
608 points by mustache_kimono | 339 comments
Linux kernel mailing list post by Greg Kroah-Hartman arguing that writing new kernel code and drivers in Rust eliminates common C bug classes, in the Rust kernel policy thread.
512 points by cyclopeanutopia | 581 comments
An essay arguing that the C++ community has split into two factions with diverging needs, ending hopes for a single dialect-free C++.
436 points by thunderbong | 96 comments
Blog post by withoutboats explaining Rust's Pin type, what pinning achieves, how it came to be, and the current problems with it.
318 points by Dunedan | 154 comments
Let's Encrypt blog post announcing its deployment of ntpd-rs, a memory-safe Rust NTP implementation from the Prossimo project, across its infrastructure.
365 points by modernerd | 122 comments
Blog post by Evan Ovadia presenting results and benchmarks from Vale's first prototype of immutable region borrowing for reducing memory safety overhead.
328 points by itvision | 172 comments
Neowin news article reporting a senior Microsoft executive's statement that the Windows 11 kernel will soon boot with Rust code inside.