Colyseus: 1.0.0: Should we deprecate Fossil Delta?

Created on 26 Apr 2019  ·  5Comments  ·  Source: colyseus/colyseus

Hey guys, as we're moving towards 1.0.0 (~August maybe?), I'd like to reduce the complexity as much as possible on the next version that will contain breaking changes.

So I'd like to know if you're okay with the deprecation of Fossil Delta?

I believe there's nothing you can do with Fossil Delta that you cannot do with the Schema, and the strong types with it play much nicely with C# and other languages.

Feel free to suggest if you'd like to see improvements on how to use the Schema.

👍 DEPRECATE Fossil Delta on 1.0.0

👎 SUPPORT Fossil Delta on 1.0.0

❓ question

Most helpful comment

I'm fine with deprecating Fossil Delta but consider doing so only after all official clients have at least a stable support for Schema ex. the haxe client currently doesn't support Schema

All 5 comments

I think when users will see the performance growth comparing FossilDelta vs Schema, the voting will be obviously!

Fossil delta is more simple and handy. So if it doesn't need too much effort, I think is a good option to have

I'm fine with deprecating Fossil Delta but consider doing so only after all official clients have at least a stable support for Schema ex. the haxe client currently doesn't support Schema

What is performance difference between Fossil Delta and Schema ? Or where I can read about it ? Thank you.

I prefer Fossil Delta but would be fine if it was easy to use as a third-party plugin. Don't prefer the heavy-handed typeness and verbosity of the default serializer.

Was this page helpful?
0 / 5 - 0 ratings