4 ms·
Show HN: Valk – new programming language with a stateful GC
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.
- boxed 8mo ago> 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 You should probably describe what you mean by that somewhere. Because on its face it doesn't seem to make sense. If you don't need to scan, why is the benchmark "how many times can we scan?"? How is this different from ARC/ORC or something more like that?
- lorenzv 8mo agoIt doesnt do tracing(scanning) to find memory that is no longer used. There's still logic that has to run that frees up memory. ARC : cycle problems ORC : Not much information is available, i can only find things about nim, but there seem to be alot of problems with it according to certain articles. Not sure if true, but this seems something completely different than what we do.
- Panzerschrek 8mo agoGC is a dead end for performance-critical software. It can't be faster than owner-based memory management.