[ChadNauseam]

I'm glad to hear it as I'm very interested in Unison. (I've been watching them from the sidelines for ages.) For those not in the loop, it's a language where your code is stored on disk in AST form, not textually. The AST representation is smart in many ways - for example, renaming a function is an O(1) operation, regardless of how often the function is used. They also have a way to serialize Unison functions and send them over the wire to other Unison programs, which is pretty sick. Their site is here: https://www.unison-lang.org/

(I'm mostly interested in it because I think it would be an ideal language for videogame scripting & modding)

[stachudotnet]

FWIW we also store ASTs, not text. We offer many of the same benefits. Some day (soon?) I'll write up a full comparison between the two, because it seems a common ask.

[conartist6]

I'd love to see where BABLR falls in that comparison. We're trying to take the same kinds of tricks and bring them to every programming language at the same time

[rienbdj]

I can’t see teams adopting Unison (or similar languages) without a way to store code in Git.

Maybe the editor can load text and do structured editing. Maybe the runtime can send functions across the network. Great. But not using Git for storage and review is just too alien for most teams to even consider.

[zahlman]

> it's a language where your code is stored on disk in AST form, not textually.

Doesn't this result in vendor lock-in for editing the code?