You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current property setup uses FASTJSON2 for de-/serialization of property values.
Initially, FASTJSON2 was selected because it was faster and purely used internally. However, given that we now expose (parts of) our serialization system to external plugins, we should re-evaluate whether this is still the right library for us.
Serialization performance is no longer the primary factor, as it should also be easy to use for external plugins.
While FASTJSON2 is pretty easy to use overall, it has two significant disadvantages:
The general Minecraft plugin ecosystem uses Gson as it is packaged with Spigot by default.
FASTJSON2's documentation is awful and there is a severe lack of examples available, which isn't the case for Gson.
The current property setup uses FASTJSON2 for de-/serialization of property values.
Initially, FASTJSON2 was selected because it was faster and purely used internally. However, given that we now expose (parts of) our serialization system to external plugins, we should re-evaluate whether this is still the right library for us.
Serialization performance is no longer the primary factor, as it should also be easy to use for external plugins.
While FASTJSON2 is pretty easy to use overall, it has two significant disadvantages:
This is a follow-up to PR #896
The text was updated successfully, but these errors were encountered: