HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
jevko
examples
OPEN SOURCE2022–2022
jevko / examples

examples

Examples of information encoded with Jevko.

2Distinct people
2Mentions
0Explicit recommenders
3GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Examples of information encoded with Jevko.

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 1:49:46 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by 6-hour interval2 dated mentions

Observed mentions: 2022-10-25 17:02:31 UTC to 2022-10-30 15:25:28 UTC.

012022-10-25 12:00:00 UTC to 2022-10-25 18:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsOct 25, 12:002022-10-25 18:00:00 UTC to 2022-10-26 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-10-26 00:00:00 UTC to 2022-10-26 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-10-26 06:00:00 UTC to 2022-10-26 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-10-26 12:00:00 UTC to 2022-10-26 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-10-26 18:00:00 UTC to 2022-10-27 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-10-27 00:00:00 UTC to 2022-10-27 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-10-27 06:00:00 UTC to 2022-10-27 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-10-27 12:00:00 UTC to 2022-10-27 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-10-27 18:00:00 UTC to 2022-10-28 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-10-28 00:00:00 UTC to 2022-10-28 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsOct 28, 00:002022-10-28 06:00:00 UTC to 2022-10-28 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-10-28 12:00:00 UTC to 2022-10-28 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-10-28 18:00:00 UTC to 2022-10-29 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-10-29 00:00:00 UTC to 2022-10-29 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-10-29 06:00:00 UTC to 2022-10-29 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-10-29 12:00:00 UTC to 2022-10-29 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-10-29 18:00:00 UTC to 2022-10-30 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-10-30 00:00:00 UTC to 2022-10-30 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-10-30 06:00:00 UTC to 2022-10-30 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-10-30 12:00:00 UTC to 2022-10-30 18:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsOct 30, 12:00

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Oct 25, 12:002022-10-25 12:00:00 UTC2022-10-25 18:00:00 UTC101
Oct 25, 18:002022-10-25 18:00:00 UTC2022-10-26 00:00:00 UTC000
Oct 26, 00:002022-10-26 00:00:00 UTC2022-10-26 06:00:00 UTC000
Oct 26, 06:002022-10-26 06:00:00 UTC2022-10-26 12:00:00 UTC000
Oct 26, 12:002022-10-26 12:00:00 UTC2022-10-26 18:00:00 UTC000
Oct 26, 18:002022-10-26 18:00:00 UTC2022-10-27 00:00:00 UTC000
Oct 27, 00:002022-10-27 00:00:00 UTC2022-10-27 06:00:00 UTC000
Oct 27, 06:002022-10-27 06:00:00 UTC2022-10-27 12:00:00 UTC000
Oct 27, 12:002022-10-27 12:00:00 UTC2022-10-27 18:00:00 UTC000
Oct 27, 18:002022-10-27 18:00:00 UTC2022-10-28 00:00:00 UTC000
Oct 28, 00:002022-10-28 00:00:00 UTC2022-10-28 06:00:00 UTC000
Oct 28, 06:002022-10-28 06:00:00 UTC2022-10-28 12:00:00 UTC000
Oct 28, 12:002022-10-28 12:00:00 UTC2022-10-28 18:00:00 UTC000
Oct 28, 18:002022-10-28 18:00:00 UTC2022-10-29 00:00:00 UTC000
Oct 29, 00:002022-10-29 00:00:00 UTC2022-10-29 06:00:00 UTC000
Oct 29, 06:002022-10-29 06:00:00 UTC2022-10-29 12:00:00 UTC000
Oct 29, 12:002022-10-29 12:00:00 UTC2022-10-29 18:00:00 UTC000
Oct 29, 18:002022-10-29 18:00:00 UTC2022-10-30 00:00:00 UTC000
Oct 30, 00:002022-10-30 00:00:00 UTC2022-10-30 06:00:00 UTC000
Oct 30, 06:002022-10-30 06:00:00 UTC2022-10-30 12:00:00 UTC000
Oct 30, 12:002022-10-30 12:00:00 UTC2022-10-30 18:00:00 UTC101

What Hacker News says

2 sources
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
Read the rest
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.
In Jevko: a minimal general-purpose syntax

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.