Slide 68 indicates latest Rails version is 1.1.6. The document was uploaded on 19 June (I'm guessing 2007). Is this really relevant now?
I will tack on that the framework will not make or break your idea. The advantage of one framework over another should be weighed in how long it takes your team to go to market; this translates into asking your development team (or yourself) what they (or you) can handle in the coming months in anticipation of the project taking off. Also your code should be done in such a way that you can ditch whatever framework you currently use for something better suited for what your future requirements might be.
I will add that I believe TurboGears to be the better platform all around, but am sticking to Rails because:
1) I like Ruby/Rails
2) I don't have the time/energy to dive into Python/TurboGears
3) I can implement something by myself confidently in Rails RIGHT NOW, as opposed to a few months down the road after getting comfy with Python (while at the same time maintaining my day job and OTHER life responsibilities)
I will tack on that the framework will not make or break your idea. The advantage of one framework over another should be weighed in how long it takes your team to go to market; this translates into asking your development team (or yourself) what they (or you) can handle in the coming months in anticipation of the project taking off. Also your code should be done in such a way that you can ditch whatever framework you currently use for something better suited for what your future requirements might be.
I will add that I believe TurboGears to be the better platform all around, but am sticking to Rails because:
1) I like Ruby/Rails
2) I don't have the time/energy to dive into Python/TurboGears
3) I can implement something by myself confidently in Rails RIGHT NOW, as opposed to a few months down the road after getting comfy with Python (while at the same time maintaining my day job and OTHER life responsibilities)