An overdue status update on Darklang

blog.darklang.com

17 points·stachudotnet··3 comments

I think there's a general pattern that, in a world where there are text-based general purpose AI code generation tools, environments that don't expose text are going to miss out. That was true even before AI, and made a custom editor like Darklang's a problem, but it's just become more true.

But the evolution as a whole does leave me wondering: where will the magic be? Will this just look like yet another language, with versioning and release processes, database connections, blah blah... like every other language, only this one is small and weird and different?

Hi there!

> Will this just look like yet another language, with versioning and release processes, database connections, blah blah... like every other language, only this one is small and weird and different?

no.

Darklang is still deployless, with no infra setup, and centered around trace-driven debugging. All the good stuff that made the product good. We just got rid of our editor, and weren't clear enough in the post that we're maintaining all of the good stuff, but putting it into a different box. Will clarify further in the next post, thanks for your input.

We've just shared an overdue update on our journey. This past year, we've been reimagining Darklang, focusing on a new CLI runtime and embracing AI.

Reply on news.ycombinator.com