tree VS make-link-text.js

Hey! I started on the data modeling language Link, which doesn't do much by itself. I am going to use BaseLink for the compiler, at first just compiling to JavaScript.

I agree that it feels like multiple projects are converging on something that is ripe (or close).

I have done some deep-digging for markup languages and came across more than one project in this space. (I've added Jevko to my list; https://twitter.com/abathur/status/1582492437984837632)

You may have already seen it as well, but you might also find https://github.com/teamtreesurf/link interesting.

You choose all of the terms in the tree, like you would choose XML tags. The linked GitHub repo and corresponding organization page explain more details.

I have a basic parser to convert the Link text into a JSON tree. I had a rough draft of a basic prototype compiler here, but in the process of porting that over to BaseLink. That last link converts Link to JavaScript in a hello-world level of degree haha, didn't get anywhere near robustness yet, I'm still a beginner too. Also haven't gotten around to doing the typechecking portion yet either.

So LinkText is simply a hierarchical set of notes/thoughts/code/etc.. A simple parser would take the tree and parse it into term/text/code/nest nodes. It is then up to you to figure out what they mean.

It's nothing fancy, just an indentation-based note-taking scheme for defining specifications or even writing code. It's parsing/handling is no more sophisticated than a JSON parser, as it literally is just parsed into a simple "term and text tree". From that point it is up to the person to resolve how to interpret the tree. On some level, it is just like a trimmed downed cleaned up version of XML, without attributes.