stevenschlansker commented on issue #2422: URL: https://github.com/apache/fory/issues/2422#issuecomment-3084756345
It is too bad, the entire ecosystem ends up being held back by Java 8 support - we cannot use the latest Java nor Arrow features, and end users end up getting much worse performance sticking on outdated technology. And when there is an Arrow CVE we are not able to mitigate by upgrading anymore. Fory ends up stuck between wishing to stay on Java 8 but depending on projects that will not support it. Fory 0.1 was only released in 2023, at which point Java 8 was already EOL for many, many years! I am a little surprised that users in 2023 would combine ancient, unsupported Java 8 with brand-new Fory serialization. But if we really have users that insist on not upgrading, I suppose there is nothing to do about it for now. It must happen eventually, though - Java 8 will not live forever. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
