Thomas Heigl

Currently there is only [this comparison](https://github.com/EsotericSoftware/kryo?tab=readme-ov-file#references) in the readme, but it focuses on throughput and not memory. For more data, you can always run `FieldSerializerBenchmark` via `KryoBenchmarks` yourself and enable...

@jhsenjaliya: Thanks for this PR. Your approach is interesting, but the changes required to support it for all types are quite invasive. I will keep this PR open for now...

I just ran into this as well. For backwards-compatibility I'm accepting the same parameter as query or as form parameter. Is there a fix and/or workaround for this at the...

This is the same issue as https://github.com/EsotericSoftware/kryo/issues/997. The user needs to register a serializer for `UnmodifiableCollection`. E.g. the one provided in https://github.com/magro/kryo-serializers.

> Do you consider adding these serializers into kryo? I was always against adding them to Kryo because they are unsafe and rely on reflection and implementation details. But so...

@mrniko: My understanding of GraalVM requirements is limited. What serializers would we need to add to the `reflect-config.json`? All of them? The issue you linked mentions `OffsetDateTimeSerializer`, but I don't...

@mrniko: Can you please create a PR with your suggested changes? Then we can discuss this further. We could add some conditional declarations for serializers: `RecordSerializer` only makes sense for...

@mrniko: We have two options here: 1. Disable unsafe on GraalVM with `-Dkryo.unsafe=false`. 2. Change the code in Kryo to use direct assignment to `static final` fields, so GraalVM can...

Note to myself: Here is how Netty handles this: https://github.com/netty/netty/blob/4.1/common/src/main/java/io/netty/util/internal/PlatformDependent0.java

See #884 for the discussion about `RecordSerializer` vs `FieldSerializer` for records.