Using Flink Tuple vs Pojo Like For Serializing Classes

[YarinOmesi]

Hi
I have gone through this repo, and i have intentions of using this library in my team production code.
I want to help making this library more robust and feature rich, and I have and idea of a change to the implementation for first supporting null fields, and more features in the future.

Before I open a PR,
I want to understand from you why you choose using Flink tuple of the implementation instead of other alternative like Pojo similar TypeInfo/Serializer ?

[cyberdelia]

We choose "tuple" because:

• Kotlin data classes are promoting immutability.
• Overall tuple implementation appeared to be faster than pojo ones.
• Tuple serialization makes it somewhat easier to evolve the schema.
  This library is also used in production already, FYI.

You're welcome to add a Pojo style serializer, as long as schema evolution quirks are well documented.