Gossamer promises “pause-free” memory and real goroutines — then ships a reference counter and a Rust compiler

The wish-list language

Gossamer bills itself as “a Rust-flavoured systems language with real goroutines and automatic, pause-free memory.” The feature list is seductive: Result/Option, exhaustive match, traits and generics with “no null”; genuine goroutines via go and typed channels on an M:N scheduler with “no async, no await, no function colouring”; and memory managed by “deterministic reference counting paired with arena { } regions — no borrow checker, no lifetimes, no stop-the-world collector.” One reader called it exactly the thing he'd been yearning for: “Kotlin without the Java baggage … Rust but with automated memory management … Go with a modern type system.”

“Pause-free” meets a 10,000-node graph

The central claim didn't survive contact with someone who knows GC theory. A commenter who picked apart the memory model was direct:

“Gossamer has a cycle collector and eager reference counting. Good luck dropping the last reference to a 10,000-node graph, especially if cyclic. That means it doesn't have 'pause free' memory.”

His point: eager refcounting can stall hard when a large object graph is freed, and the field already has genuinely pauseless GCs (ZGC and friends) that this design ignores rather than improves on.

The self-hosting tell

The most damning structural critique was a single observation about provenance. A reader flagged it as a red flag for anything calling itself a systems language: “it isn't used for its own compiler. The compiler is written in Rust. A systems programming language should be able to self-host.” Layered on top, a detailed migration-guide reading noted no user macros, no unsafe, and no move semantics — i.e. “no low level programming,” which makes “Rust-flavored systems language” a stretch. The honest summary came from a reader who liked it anyway: it's “only 2 months old … clearly vibe coded,” and crazy that such a thing can exist at all — which is its own statement about where language design is heading, even if Gossamer itself isn't the one that gets there.