Frankly speaking, if a user doesn't read documentation, XML or PHP won't help him much too especially with a plain text editor.
The problem I faced in Symfony 1 is that many times I found my answer by looking into *.yml (shipped with the library, NOT those generated for my project/app) or *ConfigHandler to truly understand the behaviour of a configuration option, rather than online doc. I reckon this can be done better in Symfony 2, by improving the documentation IN the YAML file (php.ini and httpd.conf are good examples). Yuen-Chi Lian | www.yclian.com "I do not seek; I find." - Pablo Picasso On Sat, Sep 25, 2010 at 1:38 PM, Fabien Potencier < [email protected]> wrote: > On 9/24/10 10:13 PM, Brandon Turner wrote: > >> I tend to agree with Jon here. Fabien, can you explain why the need >> for a YAML parser is a show-stopper for YAML being the default? >> > > I've done many symfony workshops. And here is what I see during these > workshops: > > * People do NOT have any IDE (so many people just use Notepad !) -- so XML > is probably not an option for them; > > * But YAML is HARD to get right. > > Here is a YAML file: > > foo: > bar: foobar > > 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. > > So, YAML being the default is nice if everything goes fine BUT as soon as > you make a typo, you are going to loose people pretty fast. > > Of course, the documentation can explain the common problems with YAML > (that's what we have in the current symfony documentation); but frankly, > people do not read documentation and even if they do, they won't remember to > check the troubleshooting section when they have a problem. Why? Because > they won't even understand that the problem is in the YAML file. > > To sum up, I'm against YAML because of my experience as a symfony trainer. > > Fabien > > > -- > 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
