easyjevko.lua
writing
easyjevko.lua | writing | |
---|---|---|
5 | 2 | |
0 | 3 | |
- | - | |
10.0 | 8.0 | |
over 1 year ago | about 1 month ago | |
Lua | HTML | |
MIT License | - |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
easyjevko.lua
-
Jevko: a minimal general-purpose syntax
Now if you take the simplest possible format built on Jevko, e.g. https://github.com/jevko/easyjevko.lua which specifies the conversion of jevkos to Lua tables and strings then an empty jevko is always converted to an empty string. Empty tables or nulls are simply prohibited in this format.
writing
-
Jevko: a minimal general-purpose syntax
I had the same idea. Simple enough, but still. Brackets are simpler to formalize and implement and not harder to explain.
> They also put some thought into designing a query language for their rose-tree-like data model, which might be adaptable to Jevko — though they label only nodes, and Jevko labels both nodes (with suffixes) and arcs (with prefixes).
Yes, that might be interesting to look at, thanks for pointing it out. I have thought about this and came up with some ideas, but haven't decided on anything. I was thinking more along the lines of having the path DSL be simply implemented on top of Jevko, not as a completely separate grammar.
> Maybe that's the subtitle for Jevko? "A minimal Unicode syntax for ordered trees with labeled nodes and labeled arcs." If that's the intended semantics it would be pretty easy to whip up a diagram in Dot to illustrate it.
It's a nice description, but I think a little to detailed and technical to fit into a tagline. Maybe a little explanatory article with the diagram included. Would probably look something like this:
https://github.com/jevko/writing/blob/main/2022-01-10-jevko-...
Although I'd gladly see your take on it. ;)
What are some alternatives?
jevkalk - A Jevko-based interpreter.
binary-experiments - Experiments with various binary formats based on Jevko.
yapl - YAml Programming Language
markup-experiments - A collection of experiments with Jevko and text markup.
moiva - A Universal tool to Evaluate, Discover alternatives and Compare Software projects.
techscriptor - Markdown editor for technical writing.
specifications - Specifications related to Jevko.
jevko
community - Features Jevko-related things created by various authors