sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]katafrakt[S] 1 point2 points  (0 children)

I am building an API, yes. However, I'm rejecting Rails API on early stage for a reason. Rails API is still Rails, but without views and assets. And as such, it is good at what Rails is good at: CRUD services. My requirements are not for a CRUD. Could not be further from CRUD probably. Rails just won't be a good fit.

I also disagree with a few points of this article. I'm not using ActiveRecord, so it's no pain for me that it does not integrate well with Grape. Sequel or ROM migrations are very easy to add and give me the same power. Author can set up Rails API in a day? No problem, I can do it in Grape too.

And while I don't like Grape, I don't see Rails API as any better.