The first of all my recent Hanami writing is out: a State of Hanami update! And there’s some exciting stuff therein: https://hanamirb.org/blog/2024/12/10/state-of-hanami-december-2024/
I’m looking forward to our project being a lot more communicative this year. This is just the start!
=> More informations about this toot | More toots from timriley@ruby.social
@timriley This is awesome, Tim. Thank you for all your hard work!!
I wonder if you have any tips on incremental adoption? My colleagues and I use a bunch of the DRY libs in significant ways and are very appreciative of the composition of Hanami, but it's been tricky to get started in the professional context. While it's largely a mental barrier, not a Hanami thing, I'm wondering if you have suggestions for low-risk forays? Would you recommend mounting a Hanami app inside of an existing Rails app, maybe separated along domain (à la DDD)? Any other suggestions?
Much thanks in advance! 🙏
=> More informations about this toot | More toots from robyurkowski@oceanplayground.social
@robyurkowski These are good questions! And I'd love to do some experimentation and help answer them in the coming months. It's things like this that I had in mind for the "Help our users be more successful" theme.
=> More informations about this toot | More toots from timriley@ruby.social
@robyurkowski Unfortunately, I don’t have any complete answers for you at this point.
Except, to say: Hanami apps (and slices) are just regular Rack apps. So mounting them inside Rails does feel like something that should be possible!
Another option would be to put a Hanami container inside Rails, and then use it as a way to manage components expressing your domain logic.
If you wanted to experiment with other of those, I’d be happy to answer questions, etc. along the way!
=> More informations about this toot | More toots from timriley@ruby.social
text/geminiThis content has been proxied by September (3851b).