grpc-dotnet VS incubator-fury

Given it's a binary serialization framework, it should not be too difficult, because the domain is well-explored and numerous libraries exist in C# which address same goals that Fury does.

More popular/newer examples are https://github.com/Cysharp/MemoryPack (which is similar to Fury with its own spec, C#-code first schema), https://github.com/MessagePack-CSharp/MessagePack-CSharp or even gRPC / Protobuf tooling https://github.com/grpc/grpc-dotnet

And I used Unity because I wanted a tool/engine that I can use to build the game for multiple platforms at once, however, after a while I realized that the game is really simple and I'm not utilizing Unity. Actually, it was quite the opposite, the performance of the game (when it comes to simple animations like drag and drop) was not that good, the size was large, and some tools like gRPC-net are not maintained anymore for Unity.

You can refer to this grpc spa example. It also demonstrates how to use grpc instead of restful API to communicate with dotnet backends.

See https://github.com/alipay/fury/blob/main/docs/guide/scala_gu... for scala serialization user doc

Yes, Game is another scenario, it's very latency sensitive. Fury is very fast for such scenarios. Actually the java implememtation has been featured by some game developers. And there has always been a demand within the community for FURY to support C#: https://github.com/alipay/fury/issues/686 . I don't have experience for c#, so c# hasn't been support. We are still the community can join us for c# support.

Arrow is a columar binary format, not a serialization framework. What fury to is convert any serializable objects to binary. Fury also defined a row format which is similar to arrow binary format: https://github.com/alipay/fury/blob/main/docs/guide/row_form...