Nicheloom

Market intelligence for builders — see what's gaining traction before it's crowded.

Valk

new programming language with a stateful GC

Details

External ID
46958684
Source
HN
Company
—
Product
Valk
Website domain
github.com
Launched
Feb. 10, 2026
Cohort
—
Upvotes
5
Upvotes percentile
0.10512129380053908
Tags
—
Fetched at
Sept. 7, 2026, 9:26 p.m.
Updated at
Sept. 7, 2026, 9:26 p.m.

Description

Greetings HN,I have been working on a new programming language for the last 3 years and thought it was time to share it with some people. The core of the language is done and i have been using it to create all software related to the language: the compiler itself, the website and vman (valk manager, like npm). There's still alot of work todo but was hoping for some feedback. Maybe an interesting feature of the language is (so i think) that it's the first language with a stateful garbage collector. It basically knows what memory goes out of scope and which doesn't without having to scan for it. So no more mark/sweep. This new GC algorithm is kind of complex and i would probably need a big blog post to explain everything. Something i will do in the future. Anyhow, feedback is welcome.

Enrichment

Theme
developer tools and programming utilities
Vertical
Horizontal
Function
Dev tools
Audience
Developer
AI stance
Not AI
Project type
Hobby / open-source project
Normalized one-liner
programming language with stateful garbage collection
Manually corrected
False

Could you build this?

No Designing and building a novel programming language with a custom compiler and a novel stateful garbage collector requires deep theoretical and systems-level compiler expertise.

What it would actually take: Building this requires a lexer, parser, intermediate representation (IR), optimizer, and backend code generator (likely LLVM or custom machine code generation), combined with low-level runtime memory management and GC state machines in C/C++ or Rust. The hardest part is correctly implementing sound type-checking, concurrency semantics, and an efficient stateful garbage collector without subtle race conditions or memory corruption bugs.

Discussion

3 comments analyzed.

Competitors mentioned: ARC (Automatic Reference Counting), ORC (Nim's memory management), Owner-based memory management

Concerns raised: Unclear how stateful GC differs from ARC/ORC, GC cannot match owner-based memory management performance, ARC has cycle problems, ORC has reported implementation issues, Benchmark methodology unclear (why measure scanning if no scanning occurs?)

Feature requests: Better documentation explaining stateful GC mechanism, Clarify distinction from existing memory management approaches

Competitors

Other products that read as similar to this one — 102 launches clear the similarity bar, closest 8 shown.

Attention rank: #97 of 103 (itself plus its competitors, highest first — normalized so YC and Product Hunt are compared fairly).

Launched 104 days after the earliest competitor.

Other launches for this product

Same idea, different domain

Nobody's really built a dev tools tool for Sales yet.