Slide 158
Slide 158 text
@vicqr
Resumen en un comentario de Github
Just saying, but to me the Symfony's serializer does not especially suffer from a bad design,
especially because its philosophy is far from the JMS serializer one. The idea of the Symfony's
serializer is to keep things simple, not trying to answer every use-cases natively, but instead
providing a great and simple architecture.
Despite the fact it offers some great features, I'm almost never using the ObjectNormalizer
and rather rely on custom normalizers (sometimes encoders) for each of my needs. Because
when I'm writing code for my application, I know exactly what the output should be. I do not
need something answering everything, just good and simple interfaces over it. This is way less
brainfucking than a JMS Serializer, as soon as you're not trying to answer very generic needs.
Now I can understand some of your concerns if you need to handle things in a very generic
way, but to me there is nothing impossible with the current architecture regarding this.
But anyway, I don't think the Symfony's serializer should try to replace entirely a JMS
Serializer. Those are simply two different tools. Use or don't use them.
https://github.com/symfony/symfony/issues/19330#issuecomment-233405451