1. 24
  1.  

  2. 7

    This is very exciting! I think Hanami is going to prove that while many Rails apps end up being slow, Ruby itself is quite fast, and the habits your framework instills in the project have a lot to do with its long-term health.

    The structural organization of code is very thoughtful; modularity in Rails monoliths takes a lot of effort, but Hanami’s Slice concept is extremely powerful. I’m already updating a production system to Hanami just for Slices.

    Another very interesting thing is that it’s modularity all the way down: all the major building blocks of the framework are useful by themselves. This feels like the promise of Merb that died with the Rails merge being reborn. You don’t have to rewrite an app from scratch to gain these benefits; I’ve been integrating the various dry-rb components for years into Rails apps.

    1. 3

      I haven’t looked at Hanami in a hot minute, but reading up on this new version and I like what I see. Not sure I’ve wrapped my head around slices, but could just be the late hour. Deps is the most intriguing to me. It seems like a better-thought-out version of an internal library in a project of mine, but I think I would have to play with it in a project to really decide how it feels.

      Congrats on the big new version.

      1. 1

        I love this not only because it is a good web app framework in it’s own right, but because it helps dispel the notion that ruby = rails. Rails and active record are lead weights holding back the reputation of ruby as the fantastic language that it has become.