The language in which the Dark interpreter is built has a GC, and we just use that.
A GC is a huge undertaking, and we already have to build an editor, a language, a stdlib, and infrastructure.
The language in which the Dark interpreter is built has a GC, and we just use that.
A GC is a huge undertaking, and we already have to build an editor, a language, a stdlib, and infrastructure.
Side note, I've written a GC in rust (stop the world, compacting). It's not a cutting edge, concurrent generational GC but it's not that big of an undertaking. And it performs very well for small problem sets since memory is all slab allocated. Only a few hundred lines in Rust.
I do definitely see how writing a tree walking interpreter is non ideal in Rust if you don't have a ton of experience writing Rust. I have a tiny lisp in Rust compared to doing it in dynamic languages it is quite verbose and hard to grok.
- we're able to deploy (safely!) in 50ms rather than minutes because of it. [1]
- we completely host the infra and you don't need to think about it (including DBs and queues, which are nicely integrated into the language) [2]
- trace driven development, where we use real values from production and show you them in your editor [2]
[1] https://blog.darklang.com/how-dark-deploys-code-in-50ms/
[2] https://darklang.com/launch/demo-video