Hacker News Reader

Comment by nerdwaller | Hacker News Reader

> I hope that RoR stays strong amidst the current React/SPA framework/Node fad.

Fortunately, rails has solid support for API only rails apps. Jbuilder is pretty great. In my experience, there’s still nothing in the node ecosystem that rivals ActiveRecord’s maturity.

View on HN

I've left the jbuilder/rabl train a while ago for ActiveModelSerializers and more recently for Netflix's fast_jsonapi. I used to like the other more document-based approaches, but after awhile I got tired of having json rendering take longer than the SQL calls. Now I can get sub millisecond view rendering while still using ruby and rails.

https://github.com/Netflix/fast_jsonapi

FYI, folks have forked fast_jsonapi to https://github.com/fast-jsonapi/fast_jsonapi as the Netflix repository has been mostly inactive recently.

Thanks for that updated link, I first saw it through the netflix repo but bundler on my project pulled from that more recent repo and I got the repos confused.

This is really cool, thanks!

Since you mentioned JBuilder

I recommend a faster JBuilder alternative:

https://github.com/malomalo/turbostreamer

Since you mention a faster JBuilder alternative,

I enjoy using jb:

https://github.com/amatsuda/jb

Don’t forget Grape and Sinatra. Plus Hanami 2.0 is around the corner and Hanami-API has fantastic performance on Falcon.

How is it "around the corner"? While having been enthusiastic about Hanami since Lotus times, I cannot help the feeling that it's more or less completely stalled at the moment. Sure, the non-functional alpha of Hanami 2.0 has been released some time ago, but nothing really happened since then (except from releasing hanami-api out of the blue). There is no timeline and Trello board seems to not be in line with state of PRs for Hanami 2.0.

I took the chance to chat to Luca Guidi at ParisRB 2020, where he did a talk about Hanami. Didn’t seem stalled to me, although I don’t expect 2.0 to be released « tomorrow ». This is not JS-land where frameworks pop up and die every day, which has a strange way of setting expectations...

Ok, that is good to know. However from my mere-user perspective it does not look so good. With Hanami 1.3 release it was announced that Hanami 1.x line won't get anything past bugfixes and security fixes, so it basically won't be developed. Instead, the work shifts to Hanami 2.0, which will include considerable number of completely breaking changes (such as different signature of actions call method). This goes on for almost 2 years now, with no clear timeline for 2.0 release. Is there a point in starting new project in Hanami 1.3 and having to completely rewrite it when 2.0 comes out? Probably not. Does it make sense to used very early-stage 2.0? Definitely not. So yeah, from my perspective the project is now in a problematic state.

Reply on news.ycombinator.com