queryjevko.js VS tree

The grammar of S-exps on the other hand, I won't quote here, but I assure you it's much more complicated. How much depends on your flavor (Jevko is also simpler in this regard: there is only one flavor, clearly specified).

There is no (intended) ambiguity around whitespace in Jevko: whitespace does not occur explicitly in the grammar. Whitespace characters are just characters. This is the defining feature of the syntax.

For this reason Jevko is more low-level: if you want to treat whitespace in some special way, you have to do that yourself. Although for most use-cases this is very similar and simple, e.g. https://news.ycombinator.com/item?id=33334314

But the point is that you can also leave it as-is, e.g.: https://github.com/jevko/queryjevko.js

or do something else -- it's up to your format.

Thank you. :)

> I wonder if I should use it for something...

I'd be honored!

A couple of ideas:

How about a simple configuration format? https://gist.github.com/djedr/681e0199859874b3324eaa84192c42... (I should make a library out of this)

Or you can put it in your query strings to make them more humane: https://github.com/jevko/queryjevko.js

Or make up a markup DSL: https://github.com/jevko/markup-experiments#asttohtmltable

Or serialize game objects in your indie game. Or make it the interface of your experimental app. Or use it to shave off a few unnecessary characters off your data: https://jevko.github.io/compactness.html

No parser in your favorite language? A basic one should be only a couple dozen lines!

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.