Wait, why are we even discussing which format total noobs will use? Who cares? They can use YAML!
I thought the discussion was about core configs and bundle authors, in which case I still believe that the explicit configuration *definition* provided by XML (w/ a XSD) is far superior to others. Unless someone hacks together the YAML validation mentioned earlier, all of the other formats are only capable of providing *defaults*, not definitions. I would like to believe that anyone writing a widely distributed bundle or any core code should be competent enough to understand a little XML. Also, bundles are very likely to rely on other bundles, and if a configuration option changes in a bundle's dependency, it would could go unnoticed unless the XSD validation is working. Of course the documentation (bundle or core) should probably *define* the available configuration options, but it would be naive to believe that documentation is always accurate and well maintained. It would be a lovely world if all documentation was perfect, but why don't we just enforce XML validation and remove the impact of bad docs altogether? I LOVE YAML, and I continue to use it for my application configs, but it's a poor choice for bundles and core code. You can't tell me it's reasonable to assume that a developer can break through all other barriers to entry and write a bundle, but can't figure out XML. If you don't understand XML, we probably don't want you in the core code messing around either. Greg -- 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
