8 ms·
I'm happy someone's challenging the Rails almost-monoculture in the Ruby ecosystem, but Hanami doesn't seem to bring much to the table. Is there anything in thi
by paozac 3mo ago
I'm happy someone's challenging the Rails almost-monoculture in the Ruby ecosystem, but Hanami doesn't seem to bring much to the table. Is there anything in this release that Rails hasn't had for years?
- itsdesmond 3mo agoWhat Hanami brings is an intentional and well-reasoned architecture that supports building maintainable applications. It has taste.
- choilive 3mo agoThat statement means nothing. You could say the exact same thing about Rails and have an equally defensible position. What about its architecture makes it better?
- itsdesmond 3mo agoYou could not.
- throwatdem12311 3mo ago“Nuh uh” Isn’t a good rebuttal. How about some examples comparing where a solution in Hanami is “tasteful” while the same solution in Rails is “not tasteful”?
- jatora 3mo agoWhat? This doesnt mean anything
- itsdesmond 3mo agoThis says more bout you than me.
- jatora 3mo agoYikes
- neko_ranger 3mo agoIt's basically the flask/fastapi but for ruby, compared to django/rails. It has it's purpose if you want to stay in ruby land
- PuercoPop 3mo agoIt is not, Hanami is a batteries-included framework. It not even a pay-as-you-go framework like Pyramid. The equivalent of Flask in Ruby land is Roda+Sequel.
- vidugavia 3mo agoI think what Hanami had to bring to the table is already on the table for years - slice architecture, repository pattern, true view layer, explicit dependency management and perhaps one that it recent - first class operations support. This release indeed does not bring a lot in that matter, rather fills the gaps in the ecosystem and DX.