Iiiinteresting. It reminds me of a hillel wayne thread from a while back that I remember poorly and can't find but will try to paraphrase.
It was like "programming languages and workflows are built around the state of having written code rather than writing code." I think the example was how in most languages you can remove a few chars or a symbol and put it in a 100% invalid state where none of the tools will work at all. A few seconds ago you had a bunch of type information, jump-to-definition, auto formatting etc, now you have a compiler error instead.
It really stuck with me because it described an experience so common I don't even really notice it anymore but really. What would it be like to work in a language that considered "non-functional" states still "valid" and tried to express what they knew about the gaps?
This is a very different idea but I feel like it's approaching some of the same concepts, in a way.Reply
Really cool UI with downright impressive polish.
Unfortunately I don't understand the language. But man, the UI looks and feels great.Reply
totally broken on mobile (Android), can't see a thingReply
I like the idea of editing AST directly instead of just plain text. JetBrains MPS is an editor based on the same principle (but much more mature). Also, the Unison language stores its code only as AST, not text.Reply
The upper-right ? leads to a Twitter thread with more detail:Reply