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
Last year jsoniter-scala migrated to JDK 11+ due to great speed up from new Math.multiplyHigh intrinsic and VarHandles that allowed using of SWAR techniques by accessing byte arrays by 64/32-bit words. For some data types it was up to 2x speed up. But some tools where it is used aim to keep JDK 8 support. Other serialization or communication libraries would like to use latest JDK APIs too, but locked to support JDK 8, so adding support of multi-release jar can unblock their evolution.
Having the ability to gather multi-release jars for different JDK versions opens seamless evolution without sacrificing the support of older JDKs.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
This was brought up by @plokhotnyuk
Background
build-server-protocol/build-server-protocol#384
Last year jsoniter-scala migrated to JDK 11+ due to great speed up from new Math.multiplyHigh intrinsic and VarHandles that allowed using of SWAR techniques by accessing byte arrays by 64/32-bit words. For some data types it was up to 2x speed up. But some tools where it is used aim to keep JDK 8 support. Other serialization or communication libraries would like to use latest JDK APIs too, but locked to support JDK 8, so adding support of multi-release jar can unblock their evolution.
Having the ability to gather multi-release jars for different JDK versions opens seamless evolution without sacrificing the support of older JDKs.
Beta Was this translation helpful? Give feedback.
All reactions