community
examples
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.
community
-
November 2022 monthly "What are you working on?" thread
If you make the parser and would like that, I'd love to feature it here: https://github.com/jevko/community
-
Jevko: a minimal general-purpose syntax
If you ever publish the project, send me a gmail at darius.j.chuck
I'd love to feature it here: https://github.com/jevko/community
examples
- Labeled ordered trees encoded with Jevko and visualized with Dot diagrams
-
Jevko: a minimal general-purpose syntax
Thank you for your feedback. Can you clarify?
What is the "first page" that you are referring to?
Can you paste a link to it along with the broken examples link?
This Hacker News submission features the blog post under this URL:
https://djedr.github.io/posts/jevko-2022-02-22.html
Clearly, you are not talking about this page, as that contains multiple links rather than a singular link.
Perhaps you are talking about the specification which is here:
https://github.com/jevko/specifications/blob/master/spec-sta...
(linked from the blog post)
and here:
https://jevko.org/spec.html
(linked from jevko.org)
All three link to Jevko examples here:
https://github.com/jevko/examples
but all these examples links seem to be correct on my end.
I agree about the importance of examples, and I try to lead with them on jevko.org and jevko.github.io (which are the front pages of Jevko -- possibly I should merge them into one).
However a formal specification is not necessarily the place to put the leading examples.
This is also where the Subjevko rule is defined. It isn't quite introduced as "known knowledge" -- the purpose of a specification is to define the unknown, more or less from the ground up. This is also why specifications tend to get a little abstract. Jevko's spec is no exception. This should be in line with expectations of authors of tools such as parsers, validators, generators, or other kinds of processors, for which the spec is the authoritative reference.
It is not necessarily the best first place to look for explanation, if you are approaching from a more casual side.
I agree that from that side a clear picture of what Jevko is and how it can be used is still lacking. I certainly should add more examples and explain the concepts with analogies.
So I appreciate the essence of your advice and hope I'll manage to improve on that.
What are some alternatives?
parsejevko.py - Simple parser for Jevko in Python.
binary-experiments - Experiments with various binary formats based on Jevko.
jevko.lua - A Jevko library for Lua.
easyjevko.lua - An Easy Jevko library for Lua.
jevkostream.scm - (WIP) Streaming parsers for Jevko in Scheme
yapl - YAml Programming Language
jevkalk - A Jevko-based interpreter.
edsl - Example of embedding TypeScript as an EDSL inside of another language
parsejevko.c - Simple parser for Jevko in C.
Glide - Glide programming language
sdk - Resurgence software development kit (SDK)