HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
rails
jbuilder
Ruby2011–2023
rails / jbuilder

jbuilder

Jbuilder: generate JSON objects with a Builder-style DSL

Web DevelopmentData & Databases
Explore on GitHubRead Hacker News discussions
7Distinct people
7Mentions
0Explicit recommenders
4.4KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Jbuilder: generate JSON objects with a Builder-style DSL

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

Observed mentions: 2011-12-01 14:12:33 UTC to 2023-03-01 00:25:15 UTC.

01232011-01-01 00:00:00 UTC to 2012-01-01 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments20112012-01-01 00:00:00 UTC to 2013-01-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments2013-01-01 00:00:00 UTC to 2014-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2014-01-01 00:00:00 UTC to 2015-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-01-01 00:00:00 UTC to 2016-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-01-01 00:00:00 UTC to 2017-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments20172018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2023

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
20112011-01-01 00:00:00 UTC2012-01-01 00:00:00 UTC110
20122012-01-01 00:00:00 UTC2013-01-01 00:00:00 UTC303
20132013-01-01 00:00:00 UTC2014-01-01 00:00:00 UTC000
20142014-01-01 00:00:00 UTC2015-01-01 00:00:00 UTC000
20152015-01-01 00:00:00 UTC2016-01-01 00:00:00 UTC000
20162016-01-01 00:00:00 UTC2017-01-01 00:00:00 UTC000
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC000
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC000
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC000
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC101
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC000
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC101
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC101

What Hacker News says

7 sources
brasic·May 7, 2022
That's completely fair. I think the analogy to SQL as an API is very apt. No one would argue that full SQL access isn't a powerful API but it takes some legwork to understand the schema and write queries to get the data you need. There's a divide between at least two types of persona here. On one side is integrators building products and features on top of the GitHub API. For these people GraphQL is arguably superior since the learning curve is manageable and in exchange for scaling it you can make an extremely specific query that returns your product's exact data requirements. The cost of writing this query is amortized over the lifetime of your integration. On the other side are e.g. users automating some part of their GitHub workflow to save themselves time. I can see how the REST API feels like a better choice here, it's certainly
Read the rest
simpler to get started with. For what it's worth, here[0] is an example of using the `gh` CLI's graphql feature to print a list of all repository URLs for a given organization by login, sorted in a relatively complicated way. It's more verbose than doing this with the REST API but significantly more flexible. This could just as easily be done with curl but as others have pointed out, pagination requires a minimal level of logic to implement, so it's more convenient to use an existing helper. This output gets flushed 10 lines at a time as pages come in, making it suitable to compose with other commands using pipes. $ gh api graphql --paginate -f query=' query($endCursor: String) { organization(login: "rails") { repositories(first: 10, after: $endCursor, orderBy: { field: STARGAZERS, direction: DESC } ) { nodes { url stargazers { totalCount } } pageInfo { endCursor hasNextPage } # needed for auto-pagination } } }' -q '.data.organization.repositories.nodes.[]' # output follows {"stargazers":{"totalCount":50643},"url":"https://github.com/rails/rails"} {"stargazers":{"totalCount":5298},"url":"https://github.com/rails/webpacker"} {"stargazers":{"totalCount":4849},"url":"https://github.com/rails/thor"} {"stargazers":{"totalCount":4075},"url":"https://github.com/rails/jbuilder"} # snip {"stargazers":{"totalCount":3},"url":"https://github.com/rails/hide_action"} {"stargazers":{"totalCount":2},"url":"https://github.com/rails/gem-buildkite-config"} {"stargazers":{"totalCount":2},"url":"https://github.com/rails/sqlite2_adapter"} {"stargazers":{"totalCount":1},"url":"https://github.com/rails/fcgi_handler"} [0]: https://gist.github.com/brasic/14222db7b3f5873b84820477cca27...
In GraphQL Is a Trap?
disbelief·Jun 30, 2012
Great story and congrats on the progress thus far! I have been building an application using a very similar Backbone+Rails stack, and your decision making at the top of the article matches up almost identically with mine. One thing I'm curious about is the performance aspect. When you say "lightening fast", I assume you're talking about the front-end user experience, since persistence to the server is performed asynchronously? The one major problem I've had with using Rails as my JSON API provider has been the performance of rendering the JSON itself. Many of my API calls return a fairly large amount of nested JSON, and the request times are far from ideal. As you mention you are placing additional data into the results for some API calls, so I guess you might have encountered this yourself. What, may I ask, are you using to render the JS
Read the rest
ON from Rails? I'm using JBuilder at the moment, which as it turns out has some performance issues: https://github.com/rails/jbuilder/issues/45
In How we used Rails & Backbone.js to build a lightning-fast webapp.

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.