+1 YAML I'm against XML, because it's horrible to read and will blow up the examples in the tutorials. YAML is easier to learn and look very nice in tutorials. And other Configurations Files have normaly also not a good error validation and help for typo's (like php.ini, http.conf), so why a Framework should do this over-engineering ? You can not avoid problems from beginners this way.
But I've some thoughts about using a "general purpose language" (ok XML is not complete a GPL but PHP is) for configuration files is always the best solution. I think a specialized DSL could do it better. Look at the XText project, they do custom DSL's with autocompletion and validation. But this is only a weired idee from me. Best wishes from Berlin, Jörg On 30 Sep., 21:52, Keri Henare <[email protected]> wrote: > The good thing about what Fabien is suggesting is that we would be able to > validate any config format independently. So rather than making XML default > (which on a side note, I am personally against) because it can be validated > against an XSD, we can validate any format anyway. > > XML is by far the most verbose of the config formats and I think that it's > verbosity makes it the most complex and the hardest for a junior to learn. -- 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
