[
https://issues.apache.org/jira/browse/DERBY-6809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16275430#comment-16275430
]
sagar commented on DERBY-6809:
------------------------------
And yes, I dont know why DERBY is a legacy product. Very stable. Mature indeed.
And trustworthy.
Kudos to all the efforts to keep it going and not moving away from CORE
STRENGTHS ... SIMPLE, ACID and STABLE.
In fact I see it being used as CLOUD based DB, MS ACCESS replacement with more
features, ORACLE EXPRESS EDITION replacement, and hope someone writes an APEX
like WYSIWYG DECLARATIVE tool for DERBY.
If I can even get started in my lifetime on any of the above, I would be at
peace with myself sitting in the CLOUDS ABOVE.
Sagar
> 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)
