grape

I'm very ambivalent about Grape, but this very much reminds me of something I do really like about it: the param validation. https://github.com/ruby-grape/grape#parameters

You are correct. Maybe the DRF for Ruby is grape https://github.com/ruby-grape/grape/blob/master/README.md but I never used it. I just fill in the standard scaffolded REST methods in the controllers with queries and write json views (Rails and Django have different terms and concepts, MVC vs MVT.)

> One metric that I'll measure a framework by is the likelihood of finding an answer to a query that is not articulated in the concepts and terms used by the framework. It's also important to measure the likelihood to have to find an answer in the first place. There are vibrant communities around many frameworks, but it doesn't make them all good. Speaking as someone who went from DRF -> Rails -> back to DRF, I can say that DRF is sufficiently confusing to understand and get started with. The problem partially exists within Django itself, but DRF doesn't exactly help. It can feel like pulling teeth to create a simple API with DRF. And, as the another HN comment explains, DRF does a ton of "opt-in" work that can end up doing more than you intended. My biggest gripe with DRF is how coupled it is to the Django ORM. All of the nice ViewSets a

Grape by Intridea https://github.com/ruby-grape/grape is a nifty choice. It is somewhat opinionated, but lightweight enough to have most of the features you'll need in writing an API Docs over at http://intridea.github.io/grape/

Let's not forget Grape either: https://github.com/intridea/grape You could see this move towards JSON APIs way back in 2012 as I suggested here: http://paulbjensen.co.uk/posts/2012/07/11/thoughts-on-rails-.... Some poo-pooed the notion, but you can clearly see that the popularity of realtime frameworks and the way that apps are built client-side heavy is pulling Rails in this direction. Performance is still the key factor here, and I suspect that's half the reason why you've got some people who espoused Ruby in the past now playing with other languages beginning with Ru, but that have a much less friendly syntax compared to Ruby. Some welcome changes though nonetheless, especially on the WebSockets front.

The typos advice is really, really good. Here's such a PR: https://github.com/intridea/grape/pull/741

This looks cool. My (current) favorite rollout for APIs with Ruby/Rack/Rails is Grape[0] with ASM[1]. [0] https://github.com/intridea/grape [1] https://github.com/jrhe/grape-active_model_serializers

I build mine on top of Grape[0] and use Swagger[1] to do a lot of the heavy lifting (also provides a web-based console); I can convert the generated Swagger docs to markdown too. [0] https://github.com/intridea/grape [1] https://github.com/tim-vandecasteele/grape-swagger

One more ruby framework that might be interesting to test would be grape. https://github.com/intridea/grape Thanks for the work you've done with bench-micro. I was not aware of all of those frameworks.

I hadn't heard of Cuba before. Grape[1] would also be worth listing in the Ruby section. It's an actively maintained microframework for REST APIs. [1] https://github.com/intridea/grape

I am writing an API in Ruby right now, and absolutely loving it. It's quick and simple. I am using Grape framework (rack based) : https://github.com/intridea/grape

We're planning to use this and it's automatically generates API docs: https://github.com/intridea/grape

> Rails should be baking in support for creating API only apps, make it easy to shed template-driven code and write UX-agnostic backends. Mobile is driving a need for creating API-only apps, and something like Asset Pipeline is an evolutionary dead-end. This has never been Rails' focus. Let Rails keep doing what it kicks ass at. Sinatra works great for API endpoints. There's probably an opportunity for an API-focused extension to Sinatra. Of course, Grape works too (https://github.com/intridea/grape). The nice thing is that all of these are built on Rack now. GitHub.com runs as a Unicorn rack app that mounts over 30 Sinatra apps and a massive Rails app together. I'm not saying this is an optimal solution, it's just where the app is at in its current evolution. But it is very possible :)

I'm most excited about the idea of automatic Client Bindings. I've been thinking about how cool it would be if you could dynamically generate a Ruby gem for your REST API, as well as a documentation site. There's already grape (https://github.com/intridea/grape) and grape_doc, so it looks like 'grape_client' is the only missing piece. Imagine being able to automatically generate versioned client libraries for ruby, php, iOS, android, etc. Would be super awesome if emergentone could get behind an open source project like that. EDIT: Welp, looks like 'swagger' is way ahead of me! http://swagger.wordnik.com/ EDIT2: The grape-swagger gem is even further ahead of me! https://github.com/tim-vandecasteele/grape-swagger

If you need to stick with Ruby for whatever reason, I recommend using Grape. https://github.com/intridea/grape