You shouldn't need more than one day to learn it.
Depends how well you want to learn it of course.
49 karma · joined March 10, 2010
Depends how well you want to learn it of course.
Sinatra (and Ramaze) also have the advantage of having been thoroughly tested and have a lot of eyeballs on them. Using Padrino (and perhaps Monk) creates the risk of (a) encountering framework boilerplate code that is buggy and (b) not having enough help to fix those problems because of insufficient resources on the part of the creators or insufficient community support.
That said, the documentation is impressive and attractive. The only suggestion I would make is the reduce the size of the downloadable screencast - no need for a 210MB video file for 12 minutes of video. Also, the version on Vimeo is unwatchable because it's not HD - it's difficult to read the source code on screen.
I'd be interested to know how Padrino compares to Monk.
At first glance Padrino seems closer to Rails in scale - which seems to defeat the whole minimalist mindset behind Sinatra. I mean, if I want Rails, I'll use Rails.
The extensive community support for Rails in combination with the improvements in Rails 3 already makes it difficult to justify using a smaller framework like Sinatra.
Many of the questions I have asked in the Sinatra community have gone unanswered so I imagine using Padrino (or even Monk) would simply add to that problem.
On the other hand, with Rails, the combination of StackOverflow, Google Groups and a plethora of Googleble web resources means you are never far from resolving a holdup.