+1 for defining the template in the extension of the file, excellent
idea Fabien!

On Sep 27, 4:16 pm, n8vo <nvonna...@gmail.com> wrote:
> Hi, I don't normally participate much in the dev list but I had to
> weigh in on this topic.  I am very grateful to all of you for your
> work on Symfony.
>
> I have to vote -1 against Twig.  I think Jonathan Wage expressed it
> well, but I want to add:
>
> I originally picked symfony, and have recommended it to others,
> because it did NOT have its own template syntax, but used familiar
> PHP.  PHP was born to mix code with HTML, to be easy and hackish.  It
> is actually not that well suited to elegant object-oriented proper MVC
> code, but it is awesome for getting things done the most direct way
> possible.
>
> The other non-PHP frameworks I evaluated had:
> * a language, like Ruby or Python or Java or C#, which is well-suited
> for OOP and MVC (unlike PHP), but which I do not know and can't
> quickly become productive with
> * a unique template language that I can't quickly produce or debug
>
> There are a lot of factors involved in choosing a technology, like
> corporate standards and ease of finding developers, but the "time from
> adoption to productivity" and "long term quality and viability" are at
> the top of my list, and symfony met them when I started with it in
> 2008.  I'm looking at that choice again now with Symfony 2, because it
> is so different, and I have to say that default use of Twig (even if
> it's possible to opt out for my own code) would make me consider non-
> PHP frameworks again.
>
> I think I understand the appeal of Twig, but in my experience, every
> template language starts out so simple, but becomes more and more
> contorted and complex (like PHP did) because at some point you
> actually need a full-featured language with full control logic,
> objects and data structures, and especially string manipulation.  Even
> in a properly designed View.  Making syntax shortcuts for the most
> commonly used embedded code is really nice, but pretty soon you end up
> with BobX (http://thedailywtf.com/Articles/We-Use-BobX.aspx).
>
> As to the wider community, was "use a template engine instead of PHP"
> a feature on the symfony 2 feature poll?  How would you measure
> something like that?
>
> Thanks for listening,
> Nathan Vonnahme
>
> On Sep 24, 9:41 am, Jonathan Wage <jonw...@gmail.com> wrote:
>
>
>
> > After thinking a bit about it. I think it is not such a good idea for
> > Symfony in the long term.

-- 
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