I'm thinking of adopting HOBO for quicker development of some Rails apps I want to develop on the side for myself.
Obviously there seems to be a certain learning curve to get the different concepts and specific coding practices of the gem and its dryml templates.
Also the documentation seems close to non-existent so I'm not sure I want to invest time in this direction but the intro screencast is very appealing to me.
Let me know of your experience of Rails + Hobo if any.
I find Hobo in some ways DRYer than Rails and more accessible to n00bs.
Having made a few web applications with Rails, and then currently working on another one I decided to try out Hobo, and I am impressed with the system. It requires extra learning, and it's hard for me to know how easy/difficult it would be to start out with Hobo if one knew nothing about Rails from beforehand. But for the next application, I'll definitively use Hobo again. Here are some of the key points that I like about it:
The claims made by the developers, that Hobo makes for a more DRY approach, and takes the convention before configuration further, is very much the case as far as I have experienced it.
I would suggest starting out by following along the tutorials. They will give a fairly clear view of what Hobo is about, and wether this is of interest to you or not.
After playing with Hobo for a while I've decided to keep developing in regular Rails.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With