Yaml configuration was also a part of symfony 1.x success. Xml is verbose and have a complex model (elements, attributes, namespaces, children nodes...). It's very complicated to remember the syntax of a configuration with XML :
- <property name="foo" value="bar" /> - <property name="foo">bar</property> - <property><name>foo</name>... XML validation is useful, but users use Notepad, but Notepad do not have a XML-XSD. Those users will be frustrated with the message "No element name expected" Yaml is more concise, easy to learn and write. +1 for Yaml as default for users with Notepad Le 26 septembre 2010 08:57, Antoine Hérault <[email protected]> a écrit : > I really love tha YAML syntax beacause it's extremely easy to read. > However, in the few projects I've done w/ Symfony2, I used XML for the > validation and autocompletion... > In my opinion, the configuration files must be readable by everyone > (project managers, integrators, etc.). That's why, once the documentation > will be there, I will use YAML. > For validation, this would be the icing on the cake! > > 2010/9/25 Davide Borsatto <[email protected]> > > On Sep 25, 6:32 pm, jeremy romey <[email protected]> wrote: >> > I like YAML for speed configuration but I think PHP is better for >> > performances... >> >> Performance is not really an issue, since every configuration (whether >> it's written in PHP, XML or YourOwnMarkupLanguage™) is eventually >> cached, so there is an overhead only on the first request, which is >> basically made by the developer anyway :) >> >> -- >> 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 [email protected] >> To unsubscribe from this group, send email to >> [email protected]<symfony-devs%[email protected]> >> 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 [email protected] > To unsubscribe from this group, send email to > [email protected]<symfony-devs%[email protected]> > For more options, visit this group at > http://groups.google.com/group/symfony-devs?hl=en > -- Alexandre Salomé http://alexandre-salome.fr -- 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 [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/symfony-devs?hl=en
