Working on a new project, is it wise to continue working on ruby on rails 3.0 or start working on 3.1?

You'll have access to the latest and greatest upgrades to the framework such as the Asset Pipeline and better engine support. Rails 3.1 is where Rails is headed, so why not make the switch now? As for staying on Rails 3.0, I don't see any reason to do that at all.

Makes sense, I would eventually have to make the switch anyway. – Amun-Ra Aug 21 at 12:14.

I as for me, I would switch to Rails 3.1, if your project is not quite large. I have 3 projects: rails 2.3.5, rails 3.0.5 and 3.1. And it is become hard to maintain older versions. When your project is not complex - you can easily migrate to fresh Rails and not fix any database or other dependencies.

Thanks, I'm at the early stages of the project but getting deep into database work. I'll make the move now. – Amun-Ra Aug 21 at 10:55 If I helped you, you can upvote my post :) – bor1s Aug 21 at 10:57.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.