Good point Ryan. >From time to time, I'm frustrated by how my developers hack around the PHP-based templates with no sense of MVC. My years of experience had taught me that you have to enforce standards at code or framework level (e.g. forcing the use of abstract classes, etc.).
When it comes to Java-based web dev, Velocity is always a better choice when compared with JSP, for the same reason. If a developer dares moving to Symfony 2 - which is paradigm-shift to many PHP developers - he or she shall be able to handle Twig. Otherwise, go back to the "conventional" PHP MVC frameworks, Symfony 1, Zend or whatever, or no framework at all. In the long run, it also forces plugin developers to adhere to the proper model and that maintains a quality pool of plugins. Yuen-Chi Lian | www.yclian.com "I do not seek; I find." - Pablo Picasso On Wed, Sep 22, 2010 at 6:56 PM, ryan weaver <weaverr...@gmail.com> wrote: I like the idea of making Twig default. It's a little bold, but Symfony2 is > bold. As mentioned, it forces you to have better separation of logic as you > can no longer "cheat" in your templates. > > > Ryan Weaver > Lead Programmer Iostudio, LLC > http://www.sympalphp.org > http://www.thatsquality.com > Twitter: @weaverryan > -- 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 developers" group. To post to this group, send email to symfony-devs@googlegroups.com To unsubscribe from this group, send email to symfony-devs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/symfony-devs?hl=en
