Hanami Blog

Hanami remains a bright spark as an alternative growing Ruby app framework to Rails. The project is under active development, I’ve met the core dev and they are lovely and much more humble than DHH and the project aims to stick much closer to the Ruby ways of doing things as opposed to the rails way. Sure the project just can’t be as mature as Rails but it deserves a look and we need to get behind projects like this if we do indeed want to see Rails alternatives flourish and grow. https://hanamirb.org/

Indeed, it seems Elixir is one part complementary to Ruby and the other a great replacement whilst also keeping the main tenets of Ruby in-place. The only issue so far is that the libraries ecosystem is indeed quite young but that is natural. Still, Ruby (even without Rails) is at the moment a more productive environment. I really hope Ruby "3x3" [0] will be released soon enough and projects like Hanami [1] become production ready so that it can coexist in a complementary way rather than becoming replaceable. [0] - https://blog.heroku.com/ruby-3-by-3 [1] - http://hanamirb.org

There is Hanami (https://hanamirb.org/) web framework which could try if Rails bothers you.

Have you looked at Hanami? https://hanamirb.org/ I'm in the same boat about RoR. I just find its size to be overkill for most uses. Hanami is considerably smaller and lightweight, but not to the point where it's more of a micro-framework (like Roda). I've been happy with it for a number of microservices and some larger websites.

I use hanami (https://hanamirb.org/) instead of Rail. My admin interface of choice is Forest (https://www.forestadmin.com/) since I cannot use ActiveAdmin outside of Rails.

Hanami[0] is a nice contrast to Rails, although not nearly as mature yet. [0] http://hanamirb.org/

Sounds good, but then someone asks: Python 2 or Python 3? And then you realize python has it's own problems... Ruby and Python are so similar though just go with one. Also, a plug for Hanami, because people are still supporting non rails frameworks despite Rails dominance. http://hanamirb.org/

This article really doesn't resonate with me. I'm excited about Hanami, but there are a few considerations that keep me from using it. First, I'd love to see that there are successful implementations of Hanami for larger "real-life" projects. On github right now the most robust Hanami app I can find is this https://github.com/ossboard-org/ossboard. Which is still a relatively simple app compared to what I tend to work on/with. Second, a while back developers in the ruby community began advocating that too many libraries/gems were Rails centric - often the gems or libs didn't work at all unless used with Rails, or non-Rails support was an after-thought. In my opinion that message seems to have hit home, and more libraries are for Ruby, not Rails, such as ShrineRB and the whole rom-rb family. Hanami's ultimate challenge, I feel, will be developing an acceptably robust ecosystem (https://github.com/davydovanton/awesome-hanami) that choosing it over Rails isn't going hurt more than the benefits of choosing Hanami. This is greatly helped by the ruby community making gems and libs for ruby, not Rails. However, in my current project while there are quite a few gems that aren't tied to Rails, there are also a number of key gems that are. I either have to roll my own or deal with alternatives that would be more work. Lastly, on the topic of Rails vs Hanami: In my view the single biggest issue with Rails right now is that the scope and complexity of web applications has grown…