Grape
Hanami
Our great sponsors
Grape | Hanami | |
---|---|---|
12 | 22 | |
9,836 | 6,178 | |
0.2% | 0.4% | |
8.2 | 7.8 | |
3 days ago | 25 days ago | |
Ruby | Ruby | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Grape
-
16 Best Ruby Frameworks For Web Development [2024]
Grape’s support extends to standard conventions, multiple format support, content negotiation, versioning, etc. The complete guide to Grape to develop REST-APIs, test the API and analyze the performance metrics is available on its official GitHub page.
-
Web Frameworks actively maintained in 2023?
Grape (ruby-grape.org)
-
An Overview of Ruby on Rails 7.1 Features. Part III
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
-
Rails api auth with Grape and Devise JWT
I am currently working on developing and api using grape and devise jwt for user user authentication.
-
Can I setup a React Native/Rails project the same way I would setup a React/Rails app, or should I expect major differences?
Your RN app will be making http requests to your server, so it doesn't really matter what backend language/framework you use. If your React work was also utilizing http requests to fetch data, then there shouldn't be much of a difference. If your backend is a simple JSON api, checkout Grape. You can tack it on to any existing Rails app.
-
Benchmarking Ruby 2.5 to 3.1 and YJIT
I've benchmarked Grape with YJIT and without it (if want to see the code, visit repo)
-
16 Best Ruby Frameworks For Web Development
Grape is a REST-like microframework written in Ruby programming language. Grape is also considered among the best ruby frameworks and can be used to run on top of Rack or can be used to complement the existing web application frameworks such as Sinatra or Rails. The latter can be done through the DSL-based REST-API for communication. The Grape ruby web framework facilitates efficient and meaningful APIs working in the web application domain.
-
Is Sinatra a good choice for a rest API
Take a look at Grape - https://github.com/ruby-grape/grape
-
What resources do you recommend to learn about Rails APIs?
I love the Grape gem for building APIs - might be worth considering if you are building something new: https://github.com/ruby-grape/grape
-
26 most popular Ruby/Rails repositories on GitHub in July-August 2020
Grape is a REST-like API framework for Ruby. It’s designed to run on Rack or complement existing web application frameworks such as Rails and Sinatra by providing a simple DSL to easily develop RESTful APIs. 9,200 stars by now
Hanami
-
16 Best Ruby Frameworks For Web Development [2024]
With a clean architectural design and a primary object methodology, Hanami is counted among the best ruby frameworks that have gained popularity as an alternative to Rails. Hanami is “sorted” in design and provides small files that can be used independently to create a project stack. Hanami is lightweight and consumes fewer resources claiming 60% lesser memory than other big Ruby frameworks.
-
Is Ruby a dying language?
No, it's just no longer over-hyped. Ruby is settling into being a mature production language, similar to Python, Java, .NET, C++, etc. As you can see from the RedMonk 2023 data Ruby is very much still alive with tons of repositories on GitHub. Besides Shopify, GitHub is another big Ruby/Rails shop. Also, besides Rails, there are other new and upcoming projects like Hanami, DragonRuby, and Ronin.
-
Web Frameworks actively maintained in 2023?
Hanami 2 (hanamirb.org)
-
Enhancing development with REPLs - A practical guide
On all my application tutorials I start by setting up an application level REPL, it's basically a console script that loads all the files inside your project, if you're using a framework like Ruby on Rails or Hanami you already have a console by running the command console also.
-
Why are there so many Rails related posts here?
This is something that kind of annoys me; there's even a /r/rails sub-reddit specifically for Ruby on Rails stuff. Understandably Rails helped put Ruby on the map. Before Rails, Ruby was just another fringe language. Rails became massively popular, helped many startups quickly build their Web 2.0 sites, and become successful companies (ex: GitHub, LinkedIn, AirBnB, etc). Like others have said, "Rails is where the money is at". However, this posses a problem for the Ruby community: whenever Rails becomes less popular, so does Ruby. I wish the Ruby ecosystem wasn't so heavily centralized around Rails, and that we diversified our uses of Ruby a bit. There's of course Sinatra, dry-rb, Hanami, Dragon Ruby, SciRuby, and a dozen security tools written in Ruby such as Metasploit, BeFF, Arachni, and Ronin.
-
Two months into learning Ruby, it is the most beautiful language I ever learned
Welcome! Ruby isn't exactly "dying", but the hype/popularity is definitely fading. This is primarily because Ruby is no longer "new", most of Ruby's popularity came from Rails, and now Rails is no longer the "new hotness". However, Ruby still has lots of awesome features and lots of awesome other libraries and frameworks, such as the new fancy irb gem that uses reline, nokogiri, chunky_png, the async gems, Dragon Ruby, SciRuby, Ronin, and the new Hanami web framework.
-
OOP vs. services for organizing business logic: is there a third way?
Data Oriented Web Development with Ruby (upcoming book) by Peter Solnica, who is on the Hanami core team. Learning Hanami wouldn't be a bad idea either.
-
Understanding Clean Architecture with small Ruby libraries
After about 5 laps around Clean architecture since I came across hanami/hanami: The web, with simplicity., I'm finally getting it down in my gut, so I'll summarize.
-
Utilizando o padrão interactor no Ruby on Rails
View on GitHub
-
Writing a web application in pure Ruby (no framework)?
If it’s just an issue with Rails, then might I suggest looking at https://hanamirb.org - it’s a framework, but one built from the lessons learned from rails and all who followed.
What are some alternatives?
Rails::API - Rails for API only applications
Sinatra - Classy web-development dressed in a DSL (official / canonical repo)
jbuilder - Jbuilder: generate JSON objects with a Builder-style DSL
Roda - Routing Tree Web Toolkit
graphql - Ruby implementation of GraphQL
Ruby on Rails - Ruby on Rails
Fast JSON API - No Longer Maintained - A lightning fast JSON:API serializer for Ruby Objects.
Padrino - Padrino is a full-stack ruby framework built upon Sinatra.
JSONAPI::Resources - A resource-focused Rails library for developing JSON:API compliant servers.
Cuba - Rum based microframework for web development.
ActiveModel::Serializers - ActiveModel::Serializer implementation and Rails hooks
Volt - A Ruby web framework where your Ruby runs on both server and client