Symfon2 or Ruby on Rails 3 for a startup?

Question

Web development

It would seem a stupid question, you can solve it yourself, but it's not as easy as it seems at first glance.
I want to implement one startup idea and decide what to choose: Symfon2 or Ruby on Rails 3.
What advantages do I see towards Symfony2:
+ I have the most experience in PHP and Symfony1.4
+ have a good understanding of the new features of PHP 5.3 and the new, popular framework means earning more
Ruby on Rails 3:
+ little experience, but this is a great reason to gain it
+ knowledge of Ruby already means a great value for me as a programmer. With RoR3 - all the more so
+ less code = less problems
The soul lies equally to both.
As a result, I want to get more experience in web programming and increase my value in the labor market.
Help me decide, please.

Answer 1

I would choose RoR3 in a similar situation.
A startup is always a startup, there is a risk that it will not “shoot”. And knowledge will remain in any case.
That is, no matter how you turn it - you will not lose :)

Answer 2

Rails of course. Mmm… learning a new language, mastering a good framework… How I regret that I switched to rails a long time ago =)

Answer 3

Learning a new technology in the process of creating a new “startup” is a bad idea. Although, if the result is not important to you, it's good. But then you need to understand what you need first of all - training or results.
If the result is, then, of course, do it on what you understand, where you have your accumulated experience.

Answer 4

It is very important to get fun from routine coding, at least due to the “cool” syntax, it helps to maintain motivation at the proper level.

Answer 5

I would choose Symfony, for practical and purely my own reasons)
Although I can’t say anything against the rail.

Answer 6

IMHO, the question here is different. How much do you value your startup and what do you want to get from it? if you are sure that a startup will really bring money and almost immediately (startup business), then choose what will help you get results the fastest, and learn ruby ​​later. If your startup is more social than commercial in nature (something like a social network where money will come only with investors and advertisers, which means not soon), then you can afford to indulge in a new language. In general, it depends on your approach to a startup and vision of its future.

Answer 7

I myself struggled with the choice, until I decided this way - the prototype is on rails, the project itself - how the map will fall :)
One of the main criteria for choosing a rail so far is that there is no regular admin panel / scaffolding generator in symphony2. For the project, this is not particularly relevant (you still write everything with pens), but for the prototype it is important, if not decisive.
The main advantages in favor of symphony2 were:
- a well-known language (do not waste time on trifles like “how to write a hash cycle”), a standard library (do not waste time on “is there strtoupper here”, but immediately google what is called and what parameters accepts :) ) and tools (in particular PHPUnit)
- DataMapper + UnitOfWork from Doctrine2 (I somehow disliked ActiveRecord sharply)

Answer 8

I think scaffold is a bad selection criterion. I would choose like this - and if he shoots, will I be thrilled to write on it? And what a fun process in general.