RFC: Make new versions of pgjdbc Java8+

From: Álvaro Hernández Tortosa <aht(at)8kdata(dot)com>
To: List <pgsql-jdbc(at)postgresql(dot)org>
Subject: RFC: Make new versions of pgjdbc Java8+
Date: 2017-04-02 22:40:50
Message-ID: 393118b3-4373-3e27-6f7e-0a7f764c9c81@8kdata.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-jdbc


Hi.

Following-up on my previous own comments on this thread:
https://www.postgresql.org/message-id/47f0171d-6d34-fc12-2849-fd157d69925b%408kdata.com,
I want to raise this question independently.

Let me bring these facts to the table:

- Java 6 EOLed 2/2013.
- Java 7 EOLed 4/2015.
- Java 8 was released 3 years ago, and brought significant improvements.
- Java 9 will be (may be) released this year.
- By July 2016, Java 6 usage was less than 10% and declining
significantly, while 8 raising, according to
https://zeroturnaround.com/rebellabs/java-tools-and-technologies-landscape-2016-trends/
- Companies are version conservative, but don't want to run on EOLed
products (that's even worse).
- Java 8 may attract more development power to the driver (nobody likes
working without lambdas, streams, etc, when they are available!).
- There are fully featured versions of pgjdbc (up to and including 42)
that are JDK6-compatible, and will remain there.

What would be the reasons *not to* make *future* versions of pgjdbc
Java8+? If fixes/security patches would be backported to some Java6+
releases (like v42), I don't actually see any.

Thoughts?

Álvaro

--

Álvaro Hernández Tortosa

-----------
<8K>data

Responses

Browse pgsql-jdbc by date

  From Date Subject
Next Message John R Pierce 2017-04-02 22:56:13 Re: RFC: Make new versions of pgjdbc Java8+
Previous Message Álvaro Hernández Tortosa 2017-04-02 22:25:39 Re: SCRAM inplementation