Just my two cents. Usually a development framework or language takes around 2 years to master. I may be wrong, but I believe that the majority of the Rails users started with the framework around two years ago. Motivation is at its higher peek now, and the cost of change is getting higher.
Anyway, I think that developing with Hobo is more productive that plan Rails once you've mastered it. I think that stability and the work in progress on the documentation will play an important role in the future. Another thing that would benefit Hobo is a roadmap. If you are in the middle of a decision process, where you need to choose the technology that will be adopted for following years, you need to know where the technology is it is heading. Don't know if there is a roadmap somewhere on the Web, I've never bumped into it. Regards, Tiago Franco On Nov 25, 9:25 am, sol <[EMAIL PROTECTED]> wrote: > > Then again, I though HoboFields would be widely popular - I mean, who > > wants to write migrations by hand? But it doesn't seem to be. So go > > figure. > > That's what surprised me the most, and this is why I started reading > the Hobo intros. > > I'm pretty sure DHH uses Hobo himself, if he is home alone :) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Hobo Users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/hobousers?hl=en -~----------~----~----~----~------~----~------~--~---
