I agree that YAML is far easier to read, but at the same time harder to debug. I've also found that the flexible syntax of YAML (one line/multiline) makes it bit harder to fullly grasp. Changing a simple value is trivial, but defining more complex structures are harder.
I reallly like XML for its autocompletion/IDE-integretation/validation. I think the worst thing a frame work can do is to first teach the "quick and dirty way" (YAML), and then later tell users that you really should use XML instead. I think we should use to format that the core developers use themselves for large client projects. Neither format is so hard to learn that it would prohibit new users. If you're seasoned enough to use Symfony2, you can deal with XML files. That being said, I still use YAML for all my symfony projects, since that was the framework default, and I've never felt the need to port to XML. -gunnar lium On Sat, Sep 25, 2010 at 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-schema-in-php/ >> >> 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]<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
