czw., 27 maj 2021 o 13:29 Pierre <pierre-...@processus.org> napisał(a):
> Le 26/05/2021 à 21:24, Michał Marcin Brzuchalski a écrit : > > I don't think nowadays anyone does that without a kind of deserializer > > which > > reads the metadata of desired DTO and like Symfony's Serializer or JMS > > which just deal with such tasks!? > > Hello, > > Just for your information, we do have our own serialization mechanism in > some projects, when writing workaround around existing serializers bugs > or behaviors become too difficult, or when we want drastic speed-ups, or > want to avoid dependencies. Sometime even just because the target > production environment is not suitable for those well-known libraries > (even in the containerized dockerized, vmized world, this still happen, > sometime). > > Don't assume that everyone use X or Y library, there are some mad guys > everywhere around the globe writing their own proprietary very complex > APIs for pretty much anything when they have critical needs or legit > constraints. For example we do maintain our own database access layer > and SQL query builder, and we are pretty much anyone, just like anyone > (why wouldn't we use Doctrine or PDO ? Yet we don't). > Please take no offense. I just think it's not that common. While I do work with many integration projects most of the time already could forget about writing my own stuff for this kind of thing where I have learned to rely on community-developed components which just speeds up development and just gets the things done. I think described cases are rarely needing such function especially if it's easy to write one using reflection. My personal preference is to reduce the amount of standard library shipped than add. Cheers, Michał Marcin Brzuchalski
