60 karma · joined September 24, 2011
Coming soon: full API (someone's already building an iOS app on it), anonymous posting, authenticating against Twitter (not just Persona), Flattr integration.
No ads _ever_, monetization through Flattr, and I may eventually do a full open-source release. (My business is in training and consulting, not in running websites.)
Enjoy.
However, whenever someone says that Happy is a nice framework "for tiny webapps", I like to chime in and add that the goal for Happy is to be as simple (and thus fit for tiny apps) as Sinatra, but also a great fit for large applications as it allows for a kind of modular development style that may feel a whole lot more natural to some people than what Rails is doing (and Padrino is sadly trying to mimick): controllers actually describing behavior - no matter how simple or complex - and not URLs or individual resources.
I'm very much looking forward to finding out how much this resonates with other Rubyists. Upwards and onwards :)
I'm also the author of Schnitzelpress, a Ruby-based blog engine built with Sinatra (and optimized for hosting on Heroku and similar cloud providers), and I will be porting it from Sinatra to Happy some time soon.
To answer your question though, the way Happy works largely revolves around routing the request URL through a simple graph of controllers (instead of mapping URLs to classes, like most other frameworks do it). These controllers are essentially apps-within-apps; modular, testable, describing functionality, not data.
It's also a good Rack citizen, as each Happy controller class is also a fully functional Rack app.
Details some time this weekend.
Yeah, whatever.
(Which is what most PHP people seem to want initially - you know, before that magic thing happens where they realize that real applications need structure.)
No reason to be surprised there, right?