Personally, I'm against having Twig as the default. I've worked at
quite a few web development companies and all the frontend developers
I work with are comfortable with editing PHP templates in wordpress,
magento, ZF etc. I tried to introduce Smarty templates in 1 company
about 4 years ago and there was a backlash from the frontend teams who
complained that they recognised enough PHP to get by, but didn't see
the advantages of using a templating language. It was just as hard for
them to understand the template notation as understanding the basic
PHP (if, else, foreach etc) which they knew already from working with
other frameworks.

Also, I understand the thought behind forcing some coding standards,
but in my experience, the coders that want to put action logic in
templates are lazy so they are more likely to be frustrated that they
cant hack the templates quickly and that they have to learn new
syntax. Experienced developers are more likely to see the advantages
of investing time into learning a templating language.

I do like Twig and I'm definitely in favour of giving the user a
choice, but for me personally, easy-to-pick up PHP templates are one
of the reasons I recommend symfony to my employers, and would only
choose Twig under certain circumstances.

-ollie

On Sep 22, 8:08 pm, Dennis Benkert <spinecras...@googlemail.com>
wrote:
> I like Fabian's point. Just for simple testing needs, or some scaffolding
> tasks it's nice as a developer to use some quick php templating code.
>
> For interaction with frontend devs or designers Twig is a good choice like
> Jordi pointed out.
>
> +1 For Twig as default
> +1 Keeping the choice to use PHP if you need it
>
> - Dennis
>
> 2010/9/22 Fabian Spillner <fabian.spill...@gmail.com>
>
>
>
> > For my opinion:
>
> > Twig can be default, if it can be disabled and ...
>
> > It should be possible to have mixture of Twig and PHP templates on the
> > bundles.
>
> > For example: The backend team wants to create quickly the PHP
> > templates to test the model outputs
> > and send the work to frontend team to migrate it into Twig templates.
>
> > For me Twig as default template is important point:
>
> > The developer is forced to make the templates clean and simple for the
> > web designer.
> > He must learn to put the logic into the controller / model and not
> > into the templates.
>
> > --
> > 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<symfony-devs%2bunsubscr...@google 
> > groups.com>
> > For more options, visit this group at
> >http://groups.google.com/group/symfony-devs?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 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

Reply via email to