We should be defaulting to the PECL Yaml component if it is available as opposed to Symfony's because:
it is a performance improvement for reads (decoding)
and is YAML complient.
(Also, see #249)
We had originally talked about this way back in the beginning but it had been forgotten about.
Add a YAML class that decides whether to use the extension or Symfony. There's no point in using plugins and plugins are too heavy for this -- it's not extensible.
Also, Created Symfony issue for their invalid parsing: https://github.com/symfony/symfony/issues/16234
They seem to be aligning themselves with PECL as well:
Config save no longer throws exceptions if the config object contains an object or resource. While we could make Symfony do this, yaml_emity() doesn't do this so we can't make this a requirement.
Beta phase evaluation
|Issue category||Task|Bug because it is a performance improvement|
|Issue priority||Major, because it saves actually something|
|Prioritized changes||Yes, performance improvements|
Major, no disruption, performance improvement so allowed.