On Sep 25, 6:38 am, Fabien Potencier <fabien.potenc...@symfony-
project.com> wrote:
> bar
>    foo: barfoo
>
> Can you spot the problem here? I can because I know where to look for.
> But people can get stuck on this one for HOURS; even if there is an
> error message saying: "Unable to parse line 4 (bar).". And after 2-3
> more problems like this one with YAML, they will just hate symfony. And
> that's only if they understand that the problem is in the YAML
> configuration file.

This seems to be an argument for better YAML validation, not for
dropping it as default. People will mess up writing XML and PHP too,
and the only thing that'll save them is accurate and well-described
error messages. That's the same for any configuration format.

Others here have also pointed out that XML is much harder to read (as
a human). There so much visual clutter that only helps computers, not
people. It's a big turn-off for me. Even though I had the Propel
TextMate bundle, I still fondly remember when (sf0.6-era?) Symfony
+Propel finally offered YAML as an alternative to XML for its schema
files. Scrolling through 20 pages of XML still gives me bad
memories :) The clean visual hierarchy of YAML is a breeze in
comparison.

As for PHP-based configuration, I think there's far too much scope for
bad behaviour, and not enough guidance. Not only is it easy to get it
wrong, but it's very hard to know what the best practice is. It's hard
enough to get people not to put application logic into templates, let
alone config files. PHP's also not exactly excellent with character-
sets/encoding in PHP source code, although that's probably a rarer
worry.

So +1 for YAML, -1 for XML, and 0 for PHP :P

-- 
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

Reply via email to