db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bryan Pendleton (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-6809) Java 1.8 feature use
Date Sat, 02 Dec 2017 01:50:00 GMT

    [ https://issues.apache.org/jira/browse/DERBY-6809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16275359#comment-16275359
] 

Bryan Pendleton commented on DERBY-6809:
----------------------------------------

Oh, I think we could make a stronger statement than that? 

Surely, rewriting the 20-year-old Derby code base to take advantage of the latest features
of the Java language has *TREMENDOUS* potential.

The code could be smaller, faster, clearer, and more reliable. 

It could be much easier to add new features. 

It could allow us to use auxiliary development tools which are oriented around the latest
Java features.

However, rewriting code is (a) tedious, and, much more importantly, (b) risky.

We have a low appetite for risk, right now.

We are blessed in that we have a rich and varied test bed, with 20 years of accumulated test
suites, which can support us as we refactor and improve the code.

We are, however, also impoverished in that, being largely a mature and "legacy" product, we
have a small active developer base, particularly relative to the size and complexity of the
code base.

To seriously consider rewriting large parts of the Derby engine, we'd need to have 10-20 committed,
active developers, such as was the case when several large corporations were actively supporting
this project.

Anyway, I have no idea where I'm going with this, just wanted to share my perspective.

> Java 1.8 feature use
> --------------------
>
>                 Key: DERBY-6809
>                 URL: https://issues.apache.org/jira/browse/DERBY-6809
>             Project: Derby
>          Issue Type: Improvement
>          Components: Network Server
>    Affects Versions: 11.0.0.0
>            Reporter: sagar
>
> Suggestion ...
> Is it possible to auto modify the existing source code using tools like Netbeans, and
take advantage of the new features in JDK 1.8 for better multiuser performance and better
utilization of current day multicore processors?
> Plainly put, can we have from 11.0 onwards a version of derby which takes advantage of
the advancements and new features in java 1.8 ... 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message