fishy commented on PR #2785:
URL: https://github.com/apache/thrift/pull/2785#issuecomment-1513777235

   > So Java 8 has been removed since [May 2022 in 
Thrift](https://github.com/apache/thrift/commit/c4e96c75758d94a79dae925b1daae0c950823057),
 with the argument to start using Java 11 features. From today and onwards this 
hasn't been used (it still compiles with Java 8). Java 8 is still supported 
(for security patches) until 2030 and many projects are still using it.
   > 
   > According to Maven central many people are still on `1.16.0` or `1.14.1`: 
<img alt="image" width="703" 
src="https://user-images.githubusercontent.com/1134248/232896165-75dec1d4-00ba-4046-8fb3-2bb0e350ab62.png";>
   > 
   > I took the time and effort to come over here to create a PR, but probably 
a lot of people don't care.
   > 
   > Why add another barrier to make it even harder for people to adopt newer 
versions? I think for `parquet-mr` it is very interesting to add support for 
UUIDs. However, we can't drop Java8 yet, and the price for not upgrading is not 
that high because the new features in the later Java versions are nice to have, 
but not required.
   > 
   > If Thrift cares about interoperability, and having support across many 
languages (including versions), then we should support Java8.
   
   The price is on both sides. Yes on one side dropping the support to java 8 
means that projects still on java 8 can no longer update to newer version of 
thrift. But on the other side, not dropping the support to java 8 means that 
thrift project can not use any new feature that's introduced after java 8.
   
   This is a matter we discussed in [thrift's 
maillist](https://lists.apache.org/thread/qlrtxc1yvrzdjkf1gqd2zcnvr49lz5y7), 
@Jimexist listed some of the features we _plan_ to use that requires the 
dropping of java 8.


-- 
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]

Reply via email to