HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
jostylr
literate-programming-lib
JavaScript2015–2015
jostylr / literate-programming-lib

literate-programming-lib

The library component of literate-programming

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

What to know before exploring

What it is

The library component of literate-programming

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 8–Nov 15 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/15/2026, 10:02:05 AM 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 week5 dated mentions

Observed mentions: 2015-02-09 06:39:29 UTC to 2015-08-17 01:35:00 UTC. Weeks start Monday, UTC.

0122015-02-09 00:00:00 UTC to 2015-02-16 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsFeb 92015-02-16 00:00:00 UTC to 2015-02-23 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-02-23 00:00:00 UTC to 2015-03-02 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-03-02 00:00:00 UTC to 2015-03-09 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-03-09 00:00:00 UTC to 2015-03-16 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-03-16 00:00:00 UTC to 2015-03-23 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-03-23 00:00:00 UTC to 2015-03-30 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-03-30 00:00:00 UTC to 2015-04-06 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-04-06 00:00:00 UTC to 2015-04-13 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2015-04-13 00:00:00 UTC to 2015-04-20 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-04-20 00:00:00 UTC to 2015-04-27 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-04-27 00:00:00 UTC to 2015-05-04 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-05-04 00:00:00 UTC to 2015-05-11 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-05-11 00:00:00 UTC to 2015-05-18 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsMay 112015-05-18 00:00:00 UTC to 2015-05-25 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-05-25 00:00:00 UTC to 2015-06-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-06-01 00:00:00 UTC to 2015-06-08 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-06-08 00:00:00 UTC to 2015-06-15 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-06-15 00:00:00 UTC to 2015-06-22 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2015-06-22 00:00:00 UTC to 2015-06-29 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-06-29 00:00:00 UTC to 2015-07-06 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-07-06 00:00:00 UTC to 2015-07-13 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-07-13 00:00:00 UTC to 2015-07-20 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-07-20 00:00:00 UTC to 2015-07-27 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-07-27 00:00:00 UTC to 2015-08-03 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-08-03 00:00:00 UTC to 2015-08-10 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-08-10 00:00:00 UTC to 2015-08-17 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-08-17 00:00:00 UTC to 2015-08-24 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsAug 17

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
Feb 92015-02-09 00:00:00 UTC2015-02-16 00:00:00 UTC101
Feb 162015-02-16 00:00:00 UTC2015-02-23 00:00:00 UTC000
Feb 232015-02-23 00:00:00 UTC2015-03-02 00:00:00 UTC000
Mar 22015-03-02 00:00:00 UTC2015-03-09 00:00:00 UTC000
Mar 92015-03-09 00:00:00 UTC2015-03-16 00:00:00 UTC000
Mar 162015-03-16 00:00:00 UTC2015-03-23 00:00:00 UTC000
Mar 232015-03-23 00:00:00 UTC2015-03-30 00:00:00 UTC000
Mar 302015-03-30 00:00:00 UTC2015-04-06 00:00:00 UTC000
Apr 62015-04-06 00:00:00 UTC2015-04-13 00:00:00 UTC101
Apr 132015-04-13 00:00:00 UTC2015-04-20 00:00:00 UTC000
Apr 202015-04-20 00:00:00 UTC2015-04-27 00:00:00 UTC000
Apr 272015-04-27 00:00:00 UTC2015-05-04 00:00:00 UTC000
May 42015-05-04 00:00:00 UTC2015-05-11 00:00:00 UTC000
May 112015-05-11 00:00:00 UTC2015-05-18 00:00:00 UTC000
May 182015-05-18 00:00:00 UTC2015-05-25 00:00:00 UTC000
May 252015-05-25 00:00:00 UTC2015-06-01 00:00:00 UTC000
Jun 12015-06-01 00:00:00 UTC2015-06-08 00:00:00 UTC000
Jun 82015-06-08 00:00:00 UTC2015-06-15 00:00:00 UTC000
Jun 152015-06-15 00:00:00 UTC2015-06-22 00:00:00 UTC202
Jun 222015-06-22 00:00:00 UTC2015-06-29 00:00:00 UTC000
Jun 292015-06-29 00:00:00 UTC2015-07-06 00:00:00 UTC000
Jul 62015-07-06 00:00:00 UTC2015-07-13 00:00:00 UTC000
Jul 132015-07-13 00:00:00 UTC2015-07-20 00:00:00 UTC000
Jul 202015-07-20 00:00:00 UTC2015-07-27 00:00:00 UTC000
Jul 272015-07-27 00:00:00 UTC2015-08-03 00:00:00 UTC000
Aug 32015-08-03 00:00:00 UTC2015-08-10 00:00:00 UTC000
Aug 102015-08-10 00:00:00 UTC2015-08-17 00:00:00 UTC000
Aug 172015-08-17 00:00:00 UTC2015-08-24 00:00:00 UTC101

What Hacker News says

2 sources
I agree that functions are not usually a good one-to-one fit for abstraction. If they were, we wouldn't need variables, loops, blocks etc. Now you could argue that we don't, we should just write code in lambda calculus -- but we don't do that. Especially for languages like assembler and C-like languages, it can be very nice to single out smaller sections of code. And while for eg: C, or I suppose a macro assembler, one might be able to in-line a lot of such blocks -- having to stay at the "block-semantic"-level of the host language can make some things pretty hard to communicate to the human reader in a good way. Ruby might actually be a good candidate for "simple" literate programming, in the sense that one probably could, and perhaps sometimes should, program ruby much like smalltalk -- no method/function longer than five lines or so, e
Read the rest
xcept for the most exceptional circumstances. Even then, I think one would find patterns that would make sense to abstract out of the "function level", or "language level". At the other end of the spectrum is too much magic, just as with any meta-programming technique, such as proper macros. I had a most peculiar experience trying to write some (mostly procedural) java with noweb. It was typical intro programming stuff, basically some very simple data structures/algorithms. It was a very nice fit for literate programming, but not such a good fit for java -- while the literate program read nicely, and was well structured, the mangled java code was unwieldy -- it turned out I'd ended up generating a java program that did what I wanted. Now, that's not really a problem, we generate assembly programs that are unwieldy all the time -- but the point is it took some discipline and thought to write a literate program that was also readable in it's tangled form. Only an issue if people are expected to read/modify it in that state, obviously. And they are, as they'll have to debug it at some point ;-) > I think the code is not incidental That was a bit tongue-in-cheek -- I meant more in the sense that comments are incidental to code in most programming languages. > https://github.com/jostylr/literate-programming-lib Very nice, thank you for sharing.
In Show HN: Servasm – Literate web server in x86 assembler
One functional feature that is missing is that of having blocks in different order. Jeremy Ashkenas argues that because of functions, we do not need that reordering. I disagree with that. I do think a large part of what makes literate programming powerful is that one can easily sculpt the order of the presentation. It elevates the code and comment to telling a story for humans. I think the code is not incidental, but is part of the aspect of the story, much like in a fictional story one has descriptive passages and dialog passages. If one updates the story, both may change or perhaps just one of them. My take on literate programming, using markdown: * minimal client at https://www.npmjs.com/package/litpro * core library and docs at https://github.com/jostylr/literate-programming-lib
In Show HN: Servasm – Literate web server in x86 assembler

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.