For those unaware, this project was previously called Lotus. I think this is being upvoted because it was mentioned in the recently popular solnic[0] blog post.<p>[0] <a href="http://solnic.eu/2016/05/22/my-time-with-rails-is-up.html" rel="nofollow">http://solnic.eu/2016/05/22/my-time-with-rails-is-up.html</a>
I would love to see an intermediate framework between Sinatra and not quite as huge as Rails. Hanami could fit that bill. But it appears as if it's trying to compete with Rails, in which case I'll never bother trying to learn it, because I already have Rails. From what I've seen of the code it looks like that's the case.<p>What would be really awesome is a way to 'promote' projects. Currently, if I start a Sinatra project and I realize later that I needed Rails, I've no choice but to either re-engineer the entire project, or tough it out with Sinatra.<p>If I had an upgrade path, then I could start every project off in Sinatra, then when I start finding myself wanting more functionality, fluidly migrate to Hanami or Rails.
<p><pre><code> % hanami new bookshelf
18 files successfully created
</code></pre>
Description is a little misleading, I was expecting to see something sinatra-like but found something rails-like. It might be more apt to call it "The lightest full-featured ruby web MVC framework".<p>Obviously that doesn't make for a good tagline, maybe: "A full-featured yet light-weight web framework, for Ruby."
I'm happy to see some new ideas in Ruby frameworks but at this point if I'm going to go to all the trouble of learning a new framework I'll learn a new language too. A lot of the problems of Rails (slow, poor concurrency story, dynamic typing) are Ruby problems not Rails problems.<p>A few years ago there weren't a lot of great options but now we have Go, Scala, Clojure, C# on Linux, Elixir, Swift (maybe eventually) etc.
Has anyone been using this? What's your experience? What kind of project?<p>I am wondering if there are components for common scenarios like authentication etc?
I'd like to see some high performance ruby implementation for backend stuff (even if limited to some extent ...) sort of like what RubyMotion is for iOS/OS X.<p>I can imagine a lot of stuff that could benefit from this on the other hand I can see why it has not been done (costs, complexity etc).<p>Anyway I am sad that RubyMotion is not just as popular as Rails is. That is...very surprising...