The Goose Programming Language
Points and comments are a snapshot, not live.
Goose is a memory-safe systems language with no heap that outperforms C++ and Rust in benchmarks.
Goose achieves memory safety via compiler-managed data stacks and inline data, avoiding heap allocators, garbage collectors, and lifetime annotations. The language claims 3.3x speed over idiomatic C++, 1.16x over hand-optimized C++, and 1.12x over safe Rust in 16 benchmarks, using less memory. Features include relative references, variable-mode ADTs, built-in serialization, and threads that share no memory. It compiles to C and can run via TinyCC with no build step.
Relative references store typed, checked offsets as 1-4 bytes, making structures position-independent. A nested record of 29 bytes in Goose would require 160 bytes plus an allocation in C++. The compiler infers lifetime roots without annotations, and references remain valid through growth.
What commenters are saying
John Carmack praised Goose's automatic analysis and data stack design, noting relative references and binary structure validation enable direct memory mapping. The language's creator, aardappel, answered questions in the thread, explaining Goose was built with AI assistance based on his previous Lobster compiler. Commenters asked about stack management, memory waste from virtual memory allocations, and whether Goose forces architectural constraints.
Aardappel clarified the compiler optimally allocates arrays to address-space-reserved stacks at compile time, and that 64-bit address spaces make the design practical where 32-bit limitations hindered earlier languages. He positioned Goose as a systems language prioritizing speed, with Lobster filling a higher-level niche. Several commenters questioned whether the documentation's numbers were from complete examples.