Hi again. The S1.4 Project I developed was for a client. That means that the project would be updated only at the client's request.
It was finished about 1 month before to know about S2. But I won't never look back from now on. S2 feels like S1.4^10. There are major improvements: routing (it is more flexible); templating (Twig and template inclusion, rendering controller's response, and inheritance is a huge step forward); validations (in s1.4 it was akward). Regards! 2011/6/5 Parijat Kalia <kaliapari...@gmail.com> > Did you at any point feel the need to switch the project that you achieved > in 1.4 to 2.0 ? Understandably the upgrade is not very good , but since it > has a lot more to offer it could have been an interesting dilemma, right? > > > On Sun, Jun 5, 2011 at 11:34 AM, oscar balladares <liebegr...@gmail.com>wrote: > >> I started with S1.4, then they announced that there will be a 2.0 version. >> I achieved 1 major proyect with 1.4, then moved to 2.0. >> >> 1.4 has a lot of plugins and books and tutorials. 2.0 has good docs but >> there are much work to be done. >> >> 2.0 is moving fast, many changes has been commited, so you have to keep an >> eye on the changelog, official docs are not always in sync with >> changes. >> >> 1.4 rocks. 2.0 rocks a lot more. >> >> Evolution. Nobody wants to live in the 'legacy' era. >> >> Keep walking ;) >> >> 2011/6/4 Parijat Kalia <kaliapari...@gmail.com> >> >>> Hi guys, >>> >>> Very curious to know if people have migrated to Symfony 2.0 or are still >>> dependent on Symfony 1.4. Would love to get everybody's knowledge and ideas >>> on this. Been proficient at Symfony 1.2.9 but now that 2.0 has been rolled >>> out, I am wondering if it is a good idea to pursue a side project while >>> simultaneously learn Symfony 2.0. >>> >>> Thanks >>> >>> Parijat Kaliaz >>> >>> -- >>> If you want to report a vulnerability issue on symfony, please send it to >>> security at symfony-project.com >>> >>> You received this message because you are subscribed to the Google >>> Groups "symfony users" group. >>> To post to this group, send email to symfony-users@googlegroups.com >>> To unsubscribe from this group, send email to >>> symfony-users+unsubscr...@googlegroups.com >>> For more options, visit this group at >>> http://groups.google.com/group/symfony-users?hl=en >>> >> >> -- >> If you want to report a vulnerability issue on symfony, please send it to >> security at symfony-project.com >> >> You received this message because you are subscribed to the Google >> Groups "symfony users" group. >> To post to this group, send email to symfony-users@googlegroups.com >> To unsubscribe from this group, send email to >> symfony-users+unsubscr...@googlegroups.com >> For more options, visit this group at >> http://groups.google.com/group/symfony-users?hl=en >> > > -- > If you want to report a vulnerability issue on symfony, please send it to > security at symfony-project.com > > You received this message because you are subscribed to the Google > Groups "symfony users" group. > To post to this group, send email to symfony-users@googlegroups.com > To unsubscribe from this group, send email to > symfony-users+unsubscr...@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/symfony-users?hl=en > -- If you want to report a vulnerability issue on symfony, please send it to security at symfony-project.com You received this message because you are subscribed to the Google Groups "symfony users" group. To post to this group, send email to symfony-users@googlegroups.com To unsubscribe from this group, send email to symfony-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/symfony-users?hl=en
