I find it surprising that Padrino hasn't gained more popularity. For me, it's perfect for the times when you need something more robust than Sinatra, but lighter than Rails. (& being Rack-based it's pretty easy to port a project to either platform if needed).
For many use cases, padrino frequently looks more and more like the "just right" solution. Great work and look forward to the 1.0 release! Prioritized routes are a very useful addition.
I use Padrino exclusively now; it does everything I need while also being lightweight, fast, and modular.<p>Since I haven't played with Rails since 3 was in beta, I'm genuinely curious: from a purely technical standpoint, for what types of projects might Rails be a better choice than Padrino?
Finally I can forgot RAILS! Finally!!! Rails is riduculous: assets pipeline a lot of new stuff but... performances? Why it is slower than Rails 2 ? What mean "merging rails and merb" ? Why on every update I need to rewrite my views because helpers changed like <%= form be <% form then <%= ??? Thanks community for give us a real and much valid choice, Padrino is thin and not slow and havy as Rails.<p>Thanks!