How stable or unstable is symfony 2.0?

Question

Well, I know that this is a preview, and I know that he says that he is not yet ready for production, and yet I dare to ask a question.

I need to start creating a fairly large application, which is planned to be released live at approximately different times in 2010.

Suppose I don't release a production application until a stable version of Symfony 2.0 is released - is it a good idea (well, I agree on a viable idea) to start building an application using the 2.0 version? How likely is it that I will need to rewrite / replace the code that I wrote due to major changes in the framework?

Thanks.

Edit: another option right now is to use symfony 1.4.
I thought and tried the Zend Framework, but I refuse to invent every module, which will cost me many hours of programming (if not days / weeks).

Answer 1

From Fabien Symfony 2 presentation to symfony live: use symfony 1.4 for your next project.

On the Symfony 2 github page: things will change.

Now consider the following:

• Symfony 1.4 will be supported until the end of 2012, 2 years after the release of your project.
• Symfony 2 does not have code generation, forms, unit tests, etc., so everything that you do to hide these fields, you will have to repeat when the official paths come (which answers your second question)

as everyone has said here, go to 1.4

Answer 2

Symfony 1.3 or 1.4 is the right choice. 1.3, if you used symfony 1.0, 1.4 before, if not. I personally am not a fan of the subframe in symfony 1.1+ for many reasons, but you may find it quite acceptable. Then this is a personal choice.

Symfony 2.0 is unstable, and many of the features that it represents are not the ones that, in my opinion, will really be of interest to the developer at this point. sf2.0, however, is an impressive exercise in creating the next generation of web frameworks; but not in creating sites that you make more feature rich or easier to develop. This can make them faster and more elegant under the hood, but this is not necessarily the main advantage of the platform for the developer. An example of this is dependency injection. This is another abstraction of the already excellent symfony core code components, and its inclusion only increases my respect for the core symfony team and their achievements, but for the end user this probably leaves a lot of head scratches over the advantage.

The main advantage of Symfony when you evaluate the basic structure is the community and its plugins, and this, in my opinion, is a decisive factor for sf2.0 right now. Yes, I know that it is essentially built from "plugins", but you will not have several important plugins, I am sure, and you will either have to write them yourself or adapt existing ones. It is for this reason that you reject the Zend Framework.

However, only my opinion. I have been developing Symfony 1.0 and 1.1 (mostly 1.0) for over 3 years now, and it still hasn't let me down.

Answer 3

What a million dollars my friend asks. This is a game, simple and simple. I used several php MVCs (cake, zend and symfony), and they all work roughly the same. What's nice about Symfony is its focus on modularity, not wheel alteration and ease of use.

I can’t give examples of larger companies using it, however I personally would use it on cakePHP or Zend at this point. I feel that she has a strong community, she cannot be left (at the moment), and I generally like to work with frameworks. Which, at the end of the day, usually matters.

As I said, I don’t know how well it scales or comes out, but it is faster than cakePHP or Zend. This is a game, no matter which frame you choose, so good luck.

Answer 4

If there is anything specific in Symfony 2.0 that you need for your application, I would advise you to go with 1.4 and work with the stable version from get-go. As far as I understand, Symfony 2.0 may be absent until the very end of the year. Symfony 1.4 will be officially supported until the end of 2012, and you will have enough time to upgrade / rewrite 2.0 later if you want to.

Answer 5

I tried Symfony 2 for a week now (I’m a full-time Symfony developer), and here are the main reasons you should continue to use symfony 1.x before upgrading to 2.0:

• Twig is unstable. You cannot use form_render, form_error, etc. But it's pretty simple using the PHP view!
• Getting a custom culture (locale) is a pain in **.
• PHP templates are not fun, like Twig for coding. An example with this translation function:
  • PHP: <?php echo $view['translator']->trans('text') ?>
  • TWIG: {% trans 'text' %}
• Bad documentation

It doesn't seem so bad, but believe me ... I need so much time to debug these things in order to understand, in the end, that this was wrong inside Symfony 2 itself.

Answer 6

By the time your project is released, version 2.0 will most likely not be stable anyway. And think that version 1.4 has long-term support for a period of three years, which you can count on if you start a new project. In addition, with symfony 2.0, everything will not be the same :), it will be very different from current versions. You may not like it :), or it may not be suitable for your project.

Answer 7

Or you can just use Lithium ... you know, this is better than all the frameworks on the mentioned page ... BUT the question of readiness v2.0 is not about cake or other frameworks (as mentioned in other posts, although I decided that too get hit).

I personally wanted to use 2.0 in a large project, but most likely I get it not out of fear (always a bad reason).

My point is this. Nothing is stable. Not even 1.4. EVERYTHING In this world is subject to change, and there are always corrections and corrections for everything. If we had not used beta alpha software, ESPECIALLY in the open source community, we would never have progressed.

So. This is a risk. The trick is that you have to be good enough to deal with any problems that may arise. I think this is just the name of the game. You are either a developer who leaves and installs Wordpress and Drupal, and says, looking at me, mom, who grew up on trousers ... Or are you the type who comes out and cuts (or bleeds) the edge and sucks it and does it. Rolls with bad times and smiles (from ear to ear) during good times.

The end of the day is your job. Never let anyone tell you how to do this. You do it however you want.