HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
deosjr
deosjr.github.io
Scheme2025–2025
deosjr / deosjr.github.io

deosjr.github.io

Discover this repository through its Hacker News conversations.

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

What to know before exploring

What it is

A public description has not been verified.

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, 3:03:16 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 hour3 dated mentions

Observed mentions: 2025-06-15 18:19:44 UTC to 2025-06-16 07:44:55 UTC.

012025-06-15 18:00:00 UTC to 2025-06-15 19:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsJun 15, 18:002025-06-15 19:00:00 UTC to 2025-06-15 20:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-06-15 20:00:00 UTC to 2025-06-15 21:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-06-15 21:00:00 UTC to 2025-06-15 22:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-06-15 22:00:00 UTC to 2025-06-15 23:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-06-15 23:00:00 UTC to 2025-06-16 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-06-16 00:00:00 UTC to 2025-06-16 01:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsJun 16, 00:002025-06-16 01:00:00 UTC to 2025-06-16 02:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-06-16 02:00:00 UTC to 2025-06-16 03:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-06-16 03:00:00 UTC to 2025-06-16 04:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-06-16 04:00:00 UTC to 2025-06-16 05:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-06-16 05:00:00 UTC to 2025-06-16 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-06-16 06:00:00 UTC to 2025-06-16 07:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-06-16 07:00:00 UTC to 2025-06-16 08:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsJun 16, 07: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
Jun 15, 18:002025-06-15 18:00:00 UTC2025-06-15 19:00:00 UTC101
Jun 15, 19:002025-06-15 19:00:00 UTC2025-06-15 20:00:00 UTC000
Jun 15, 20:002025-06-15 20:00:00 UTC2025-06-15 21:00:00 UTC000
Jun 15, 21:002025-06-15 21:00:00 UTC2025-06-15 22:00:00 UTC000
Jun 15, 22:002025-06-15 22:00:00 UTC2025-06-15 23:00:00 UTC000
Jun 15, 23:002025-06-15 23:00:00 UTC2025-06-16 00:00:00 UTC000
Jun 16, 00:002025-06-16 00:00:00 UTC2025-06-16 01:00:00 UTC101
Jun 16, 01:002025-06-16 01:00:00 UTC2025-06-16 02:00:00 UTC000
Jun 16, 02:002025-06-16 02:00:00 UTC2025-06-16 03:00:00 UTC000
Jun 16, 03:002025-06-16 03:00:00 UTC2025-06-16 04:00:00 UTC000
Jun 16, 04:002025-06-16 04:00:00 UTC2025-06-16 05:00:00 UTC000
Jun 16, 05:002025-06-16 05:00:00 UTC2025-06-16 06:00:00 UTC000
Jun 16, 06:002025-06-16 06:00:00 UTC2025-06-16 07:00:00 UTC000
Jun 16, 07:002025-06-16 07:00:00 UTC2025-06-16 08:00:00 UTC101

What Hacker News says

3 sources
Thank you for the feedback! I agree with all of the above. Should've probably been a bit more clear on the dl-find syntax; I find it just as unacceptable as you do. It is the result of laziness: my intended use of this minimal Datalog does not include any querying whatsoever but abuses fixpoint analysis for side-effects (see https://github.com/deosjr/deosjr.github.io/blob/master/dynam... which I intend to go over in a future post). I initially had it working like you described but butchered it for the above and haven't repaired it yet (see https://github.com/deosjr/whistle?tab=readme-ov-file#datalog). This version relied on some monstrous eval-hacking using a homebrew Lisp, which I've mostly cleaned up now in this version (https://github.com/deosjr/whistle/blob/main/datalog/datalog.... is a crime, for example). The semantics are indeed li
Read the rest
mited to binary relations atm, which I agree is the main thing that disqualifies this as a proper Datalog. iirc the tutorial on Datalog that I based this implementation on only handled triples as well so I stopped there, but extending to N-ary relations is on my list to look into for sure.
In Datalog in miniKanren

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.