SA-21/06, C-11, Asapur, Varanasi, UP support@kamaldnp.com +91 8318013442
Technology

Goose: A Memory-Safe Systems Language With No Heap, No GC — and an AI-Built Compiler

KAMALDNP Raj Kamal
November 21, 2026
5 Min Read
5 Views
Goose: A Memory-Safe Systems Language With No Heap, No GC — and an AI-Built Compiler

Memory safety is one of the oldest problems in systems programming, and most languages solve it by adding machinery: a garbage collector, reference counting, lifetime annotations, or destructors. Goose, a new systems language by Wouter van Oortmerssen — the programmer behind FlatBuffers and Lobster — takes the opposite route. It removes all of that machinery. There is no heap allocator, no garbage collector, no lifetime annotations, no refcounting and no destructors. Values live inline on compiler-managed data stacks, and the compiler itself keeps track of where everything is.

The output is deliberately old-school in the best way: Goose compiles to a single C file, and it ships with a bundled TinyCC backend, so the whole toolchain stays small and self-contained. Version v2026.3 was released on 21 October 2026, when the repository had around 1,950 stars.

The project's own benchmark claims are striking: 3.3x idiomatic C++, 1.16x hand-optimised C++, and 1.12x the best safe Rust, plus a 29-byte record where the equivalent in C++ takes 160 bytes. Those figures should be quoted as the project's claims, with two qualifications. On the one hand, dev.to independently measured and confirmed the 29-byte record. On the other, LockerGnome notes that the benchmark file itself shows slightly different geometric means — 3.51x, 1.24x and 1.13x on the MSVC build — so the headline numbers depend on the build and the measurement setup.

There is a second story here that drew as much attention as the language design. The repository states that Goose was "produced almost entirely with AI": Claude Fable carried out the compiler implementation, the benchmarking and the documentation, working from van Oortmerssen's design. That claim sparked a meta-controversy on Hacker News over whether an AI-built repository qualifies as spam — a debate about authorship and craft that is still unresolved across the open-source world.

Key facts

ItemDetails
LanguageGoose — memory-safe systems language
AuthorWouter van Oortmerssen (FlatBuffers, Lobster)
Memory modelNo heap allocator, no GC, no lifetime annotations, no refcounting, no destructors — values inline on compiler-managed data stacks
OutputCompiles to a single C file; bundled TinyCC backend
Latest versionv2026.3, released 21 October 2026
GitHub stars~1,950 at the v2026.3 release
Project's benchmark claims3.3x idiomatic C++; 1.16x hand-optimised C++; 1.12x best safe Rust; 29-byte record vs 160 bytes in C++
Independent checkdev.to independently measured and confirmed the 29-byte record
QualificationLockerGnome notes the benchmark file shows slightly different geometric means (3.51x / 1.24x / 1.13x on the MSVC build)
AI involvementRepo states it was "produced almost entirely with AI" — Claude Fable did compiler implementation, benchmarking and docs from van Oortmerssen's design
ReceptionHacker News meta-controversy over whether an AI-built repo qualifies as spam

What this means

Goose matters for two separate reasons. Technically, it is a genuine experiment in language design: if the compiler can manage data stacks well enough, memory safety might not need the runtime machinery that other languages carry. The small-record result — 29 bytes against 160 in C++ — shows why that matters: leaner data layouts mean less memory traffic, which is often where real performance comes from. Students of compilers and systems programming will find Goose a rewarding project to read, precisely because its whole approach is so different from Rust's or C++'s.

The second reason is cultural. A respected language designer publishing a compiler "produced almost entirely with AI" — and saying so openly — forces a question the field has been circling for a while: when an AI does the implementation from a human's design, who is the author, and does the result deserve the same standing as hand-written code? The Hacker News argument about whether such a repo counts as spam is really an argument about what open source values: the idea, the implementation, or the labour. There is no settled answer yet, and Goose is now one of the clearest test cases.

For now, treat the benchmarks as the project's claims — encouraging, partly confirmed, and worth independent replication before anyone builds on them.

A note on verification

The author, design, output format, version and release date, star count and AI-production statement are as verified in the re-verify returns (21 November 2026). The benchmark figures (3.3x / 1.16x / 1.12x; 29 bytes vs 160) are the project's own claims: dev.to independently measured and confirmed the 29-byte record, while LockerGnome notes the benchmark file shows slightly different geometric means (3.51x / 1.24x / 1.13x on the MSVC build). This post will be updated if independent benchmark replications appear.

Source: Goose project repository; dev.to; LockerGnome; Hacker News. Last checked: 21 November 2026.

FAQs

What is Goose?
Goose is a memory-safe systems programming language by Wouter van Oortmerssen, creator of FlatBuffers and Lobster. It has no heap allocator, garbage collector, lifetime annotations, refcounting or destructors — values live inline on compiler-managed data stacks.

What does Goose compile to?
Goose compiles to a single C file, and it ships with a bundled TinyCC backend, keeping the whole toolchain small and self-contained.

How fast is Goose, really?
The project claims 3.3x idiomatic C++, 1.16x hand-optimised C++ and 1.12x the best safe Rust, with a 29-byte record versus 160 bytes in C++. Dev.to independently confirmed the 29-byte record, but LockerGnome notes the benchmark file shows slightly different geometric means (3.51x / 1.24x / 1.13x on the MSVC build) — so treat the figures as the project's claims.

Was Goose really built with AI?
According to the repository, Goose was "produced almost entirely with AI" — Claude Fable did the compiler implementation, benchmarking and documentation from van Oortmerssen's design. The claim sparked a Hacker News debate over whether an AI-built repo qualifies as spam.

Share this post

Comments (0)

Share your question or experience about this syllabus. Your comment will appear after review.

No comments yet — be the first to share your thoughts!

🤖 KAMALDNP AI Assistant

Ask about courses, website & more

Hi! I'm KAMALDNP AI Assistant. Ask me about our courses, website features, or anything else! 😊
Please wait 5s...
🤖 KAMALDNP Assistant ✕

Request human callback:

🔐 Login Required
✕

Please log in to download. You will stay on this page after logging in!

New here? Register now →