If we're going for ease of use, then YAML should be the "default".
I understand what Fabien says about people getting stucked with stupid mistakes, so they won't probably keep using Symfony, but the same kind of user is the one that when a XML file pops up, he gets so scared that he runs away screaming and crying :) Plain PHP on the other hand does not feel like the best approach to handle configuration. Maybe it's just me, but when I'm in the configuration writing mood, I really dislike being forced to write PHP code. Where I used to work we had kind of a framework that allowed only PHP configuration, and it was a nightmare (using conditions, loops and other stuff like that in a config file? Really?). INI and annotations are good only to show the power and flexibility of the framework, but INIs feel so old style, and annotations are too much error prone. Wrapping up, YAML should be the default, but only for its "easy looking", which IMHO is a must for beginners. On Sep 25, 11:25 am, Francois Zaninotto <[email protected]> wrote: > Not just this guy (lol), but other projects focused on that, too. > > http://www.kuwata-lab.com/kwalify/ > > François > > 2010/9/25 Lukas Kahwe Smith <[email protected]> > > > > > On 25.09.2010, at 11:01, Francois Zaninotto wrote: > > > > Lastly, if syntax and grammar are still strong points against YAML, it's > > not impossible to improve the error messages in the parsing (to help with > > syntax), or to validate a YAML file against a schema (to help with grammar). > > > > In conclusion: YAML for default. > > > yeah if we could validate YAML properly, then one of the main drawbacks is > > removed. not sure why i never googled this before, but someone seems to have > > put a lot of thought into being able to cross-compile yaml to xml to be able > > to use XSD for validation: > > >http://redotheweb.com/2008/09/09/validating-a-yaml-file-against-a-sch... > > > regards, > > Lukas Kahwe Smith > > [email protected] > > > -- > > 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] For more options, visit this group at http://groups.google.com/group/symfony-devs?hl=en
