HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
brianmario
yajl-ruby
C2009–2011
brianmario / yajl-ruby

yajl-ruby

A streaming JSON parsing and encoding library for Ruby (C bindings to yajl)

Data & DatabasesLanguages & CompilersLibraries & SDKs
Explore on GitHubRead Hacker News discussions
2Distinct people
3Mentions
0Explicit recommenders
1.5KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

A streaming JSON parsing and encoding library for Ruby (C bindings to yajl)

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 month3 dated mentions

Observed mentions: 2009-05-17 00:39:57 UTC to 2011-06-07 08:37:34 UTC.

012009-05-01 00:00:00 UTC to 2009-06-01 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 commentsMay 20092009-06-01 00:00:00 UTC to 2009-07-01 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments2009-07-01 00:00:00 UTC to 2009-08-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2009-08-01 00:00:00 UTC to 2009-09-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2009-09-01 00:00:00 UTC to 2009-10-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2009-10-01 00:00:00 UTC to 2009-11-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2009-11-01 00:00:00 UTC to 2009-12-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2009-12-01 00:00:00 UTC to 2010-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2010-01-01 00:00:00 UTC to 2010-02-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2010-02-01 00:00:00 UTC to 2010-03-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2010-03-01 00:00:00 UTC to 2010-04-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2010-04-01 00:00:00 UTC to 2010-05-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2010-05-01 00:00:00 UTC to 2010-06-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsMay 20102010-06-01 00:00:00 UTC to 2010-07-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2010-07-01 00:00:00 UTC to 2010-08-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2010-08-01 00:00:00 UTC to 2010-09-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2010-09-01 00:00:00 UTC to 2010-10-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2010-10-01 00:00:00 UTC to 2010-11-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2010-11-01 00:00:00 UTC to 2010-12-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2010-12-01 00:00:00 UTC to 2011-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2011-01-01 00:00:00 UTC to 2011-02-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2011-02-01 00:00:00 UTC to 2011-03-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2011-03-01 00:00:00 UTC to 2011-04-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2011-04-01 00:00:00 UTC to 2011-05-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2011-05-01 00:00:00 UTC to 2011-06-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2011-06-01 00:00:00 UTC to 2011-07-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsJun 2011

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
May 20092009-05-01 00:00:00 UTC2009-06-01 00:00:00 UTC110
Jun 20092009-06-01 00:00:00 UTC2009-07-01 00:00:00 UTC110
Jul 20092009-07-01 00:00:00 UTC2009-08-01 00:00:00 UTC000
Aug 20092009-08-01 00:00:00 UTC2009-09-01 00:00:00 UTC000
Sep 20092009-09-01 00:00:00 UTC2009-10-01 00:00:00 UTC000
Oct 20092009-10-01 00:00:00 UTC2009-11-01 00:00:00 UTC000
Nov 20092009-11-01 00:00:00 UTC2009-12-01 00:00:00 UTC000
Dec 20092009-12-01 00:00:00 UTC2010-01-01 00:00:00 UTC000
Jan 20102010-01-01 00:00:00 UTC2010-02-01 00:00:00 UTC000
Feb 20102010-02-01 00:00:00 UTC2010-03-01 00:00:00 UTC000
Mar 20102010-03-01 00:00:00 UTC2010-04-01 00:00:00 UTC000
Apr 20102010-04-01 00:00:00 UTC2010-05-01 00:00:00 UTC000
May 20102010-05-01 00:00:00 UTC2010-06-01 00:00:00 UTC000
Jun 20102010-06-01 00:00:00 UTC2010-07-01 00:00:00 UTC000
Jul 20102010-07-01 00:00:00 UTC2010-08-01 00:00:00 UTC000
Aug 20102010-08-01 00:00:00 UTC2010-09-01 00:00:00 UTC000
Sep 20102010-09-01 00:00:00 UTC2010-10-01 00:00:00 UTC000
Oct 20102010-10-01 00:00:00 UTC2010-11-01 00:00:00 UTC000
Nov 20102010-11-01 00:00:00 UTC2010-12-01 00:00:00 UTC000
Dec 20102010-12-01 00:00:00 UTC2011-01-01 00:00:00 UTC000
Jan 20112011-01-01 00:00:00 UTC2011-02-01 00:00:00 UTC000
Feb 20112011-02-01 00:00:00 UTC2011-03-01 00:00:00 UTC000
Mar 20112011-03-01 00:00:00 UTC2011-04-01 00:00:00 UTC000
Apr 20112011-04-01 00:00:00 UTC2011-05-01 00:00:00 UTC000
May 20112011-05-01 00:00:00 UTC2011-06-01 00:00:00 UTC000
Jun 20112011-06-01 00:00:00 UTC2011-07-01 00:00:00 UTC101

What Hacker News says

3 sources
tung·Jun 7, 2011
Digging around, I found that the author used the JSON gem, relying on to_json taking an optional generator arg. But, yajl-ruby and ActiveSupport define to_json themselves without that, leading to breakage. Those, and the fix for his project[1], are all on GitHub. The author claims most Ruby programmers are monkey-patching and causing these problems. That's almost right: they were. But by and large, they know better now, and would happily replace it with better code, if they could just find it and fix it: that's the real problem. The author could help by, say, logging an issue, or forking and pull requesting a fix. I checked GitHub; his ID, bcoe, doesn't show in the issues, nor in the pull requests of yajl-ruby's GitHub page[2]. I'm not saying he must do this for every problem with every open-source project he happens across, but even one
Read the rest
contribution helps more than this steam-venting blog post. [1] https://github.com/bcoe/tire/commit/2dd5fc03 [2] https://github.com/brianmario/yajl-ruby
In Why I hate Ruby (or at least some common practices of its developers)

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.