Yes, I thought of this issue when I name it Lambda. But I like the name 'Lambda'. Once get over the initial stage, Lambda will be easy for people to remember.

Quint is an interesting lang, and the concept of 'executable spec' is definitely the direction to go in the age of AI vibe coding.

And the language, Lambda, that I designed and implemented has many similar characteristics: https://github.com/henry-luo/lambda

thanks.

As for the performance, I'm standing on the shoulder of great tools like MIR JIT compiler.

Lambda's PDF support is still very limited at moment. I do plan to enhance it in next release.

Glad to hear that. Note that the language is still being developed, and there're bugs here and there. So bear with those bugs. But it should be fun to try it out.

Hope it will change the way people work with data and documents.

While Lambda still has a pretty static GUI at the moment. My plan is to build it into a fully interactive, editable UI on all kinds of document data.

A new notation by itself won't be useful. It's the tool stack, the eco system around it that matters. That's why I'm building beyond that the format itself. I'm building the schema, the validator, the scripting and query language around it.

Here's the XKCD 927 post from last beta release: https://news.ycombinator.com/item?id=16308803

Yes, it's a must! Have that posted in the 0.11 beta release as well. :-)