JSjshen·Jul 2, 2012
rails is moving towards a "view" based approach. Here is one of the up and coming libraries.
https://github.com/rails/jbuilder/
It looks a lot like a view file :)
In MVC is dead, it's time to MOVE onrails
jbuilder
Ruby2011–2023
rails / jbuilder
jbuilder
Jbuilder: generate JSON objects with a Builder-style DSL
7Distinct people
7Mentions
0Explicit recommenders
4.4KGitHub stars
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, 10:22:47 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.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| 2011 | 2011-01-01 00:00:00 UTC | 2012-01-01 00:00:00 UTC | 1 | 1 | 0 |
| 2012 | 2012-01-01 00:00:00 UTC | 2013-01-01 00:00:00 UTC | 3 | 0 | 3 |
| 2013 | 2013-01-01 00:00:00 UTC | 2014-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2014 | 2014-01-01 00:00:00 UTC | 2015-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2015 | 2015-01-01 00:00:00 UTC | 2016-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2016 | 2016-01-01 00:00:00 UTC | 2017-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2017 | 2017-01-01 00:00:00 UTC | 2018-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2018 | 2018-01-01 00:00:00 UTC | 2019-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2019 | 2019-01-01 00:00:00 UTC | 2020-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2020 | 2020-01-01 00:00:00 UTC | 2021-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2021 | 2021-01-01 00:00:00 UTC | 2022-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2022 | 2022-01-01 00:00:00 UTC | 2023-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2023 | 2023-01-01 00:00:00 UTC | 2024-01-01 00:00:00 UTC | 1 | 0 | 1 |
What Hacker News says
3 sourcesGreat 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
Sorry but can someone enlighten me, on why this might be be better than using:
https://github.com/josevalim/active_model_serializers,
https://github.com/nesquena/rabl,
https://github.com/rails/jbuilder
In Rethinking web API development