> What surprises me is that Hobo is not more widely known. I've been
> listening to the Ruby on Rails podcast and reading Rails websites for
> over two years and have never heard a mention of it.

Hi, someone asked me the same question yesterday in irc.

My personal experience (eg. in #rubyonrails) is that most people
think about it like "oh not another scaffolding framework" everytime
I mention it, resulting in a negative attitude towards hobo.
Hobo can't be explained in 2-3 words, so, convincing them of the
opposite is not really easy.

Another point in my opinion is that lots of people jumped on the
Hobo wagon in an early stage, where lots of things changed, and if
you don't have the time it is really hard to follow all these
changes.
Others get frustrated with Dryml because you can't jump start into
it without reading the documentation.

Nowadays Hobo is pretty stable, there is already some good
documentation (and a very nice documentation platform) and Tom is
supported by a Company.
Tom and James have already done a presentation at a rails
conference, with very positive feedback.

Maybe a Video in the style of 'App for 5 in 5 mins' would be nice
for newcomers... it's hard to see the power of Hobo by looking
at the page for 2 minutes.

The Hobo site is already included in planetrubyonrails.com, so I
guess a lot people are reading it already.
And if you like it, Blog about it, add 'featured by' footer to your
sites etc, I'm not the best example for doing that, but I have some
upcoming public Hobo apps. There is also a section "Hobo Apps in the
Wild" on the page, so be sure to submit your cool Hobo projects!

..just my thoughts about it :)

sol

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to