You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ctakes.apache.org by "Finan, Sean" <Se...@childrens.harvard.edu> on 2015/09/16 19:37:02 UTC
CTAKES-377 : Upgrade to Java 8
Can anybody out there think of a reason why we shouldn't upgrade to Java 8? Please comment on Jira.
https://issues.apache.org/jira/browse/CTAKES-377
Thanks,
Sean
RE: CTAKES-377 : Upgrade to Java 8
Posted by "Finan, Sean" <Se...@childrens.harvard.edu>.
Great feedback gang!
With plenty of "binding votes", the motion/question passes!
I haven't seen any negatives, so I will soon start using java 8 features in new and refactored trunk code. Please feel free to do the same for the next (3.2.3) release.
Upgrade now or suffer the compiler errors ...
Cheers,
Sean
-----Original Message-----
From: andy mcmurry [mailto:mcmurry.andy@gmail.com]
Sent: Friday, September 18, 2015 4:01 PM
To: dev@ctakes.apache.org
Subject: Re: CTAKES-377 : Upgrade to Java 8
+1 long live Java 8 !
On Fri, Sep 18, 2015 at 7:43 AM, Jay Vyas <ja...@gmail.com>
wrote:
> +1 for sure
>
> > On Sep 18, 2015, at 10:06 AM, Ted Strall <ts...@yahoo.com.INVALID>
> wrote:
> >
> > Going to Java 8 can provide a lot of benefit to an application like
> cTAKES.
> > The new features added to Java 8 are a game changer in terms of doing
> data pipelining. The streams functionality and the ability to do functional
> programming gives you the opportunity get 'parallelism almost for free.'
> > That means the jvm can use all the available cpu cores without the need
> to explicitly write multi-threaded code, as long as you write functional
> style code (which basically means no shared variables.) This style of
> writing code would also make it easier to transition to a distributed
> processing environment like Spark or Hadoop.
> > Of course, to get the benefit of 'parallelism almost for free' would
> require using streams when working with collections and files, along with
> refactoring important pieces of existing code to do the same.
> > 'Java 8 In Action' is a really great book to get up to speed on the new
> features.
> > From: Pei Chen <ch...@apache.org>
> > To: "dev@ctakes.apache.org" <de...@ctakes.apache.org>
> > Sent: Wednesday, September 16, 2015 2:00 PM
> > Subject: Re: CTAKES-377 : Upgrade to Java 8
> >
> > +1 upgrading to Java 8; been using it unofficially locally.
> >
> >
> >
> > On Wed, Sep 16, 2015 at 1:37 PM, Finan, Sean
> > <Se...@childrens.harvard.edu> wrote:
> >> Can anybody out there think of a reason why we shouldn't upgrade to
> Java 8? Please comment on Jira.
> >>
> >> https://urldefense.proofpoint.com/v2/url?u=https-3A__issues.apache.org_jira_browse_CTAKES-2D377&d=BQIBaQ&c=qS4goWBT7poplM69zy_3xhKwEW14JZMSdioCoppxeFU&r=fs67GvlGZstTpyIisCYNYmQCP6r0bcpKGd4f7d4gTao&m=bmpDKbbvKJ2K7SSUaWVIJ4YR44YKafrSaL_JeuXe5h0&s=elHMIae2D6nT54rRwYplh1XJDKzvSMKDjUnDxx7r20c&e=
> >>
> >> Thanks,
> >> Sean
> >
> >
>
Re: CTAKES-377 : Upgrade to Java 8
Posted by andy mcmurry <mc...@gmail.com>.
+1 long live Java 8 !
On Fri, Sep 18, 2015 at 7:43 AM, Jay Vyas <ja...@gmail.com>
wrote:
> +1 for sure
>
> > On Sep 18, 2015, at 10:06 AM, Ted Strall <ts...@yahoo.com.INVALID>
> wrote:
> >
> > Going to Java 8 can provide a lot of benefit to an application like
> cTAKES.
> > The new features added to Java 8 are a game changer in terms of doing
> data pipelining. The streams functionality and the ability to do functional
> programming gives you the opportunity get 'parallelism almost for free.'
> > That means the jvm can use all the available cpu cores without the need
> to explicitly write multi-threaded code, as long as you write functional
> style code (which basically means no shared variables.) This style of
> writing code would also make it easier to transition to a distributed
> processing environment like Spark or Hadoop.
> > Of course, to get the benefit of 'parallelism almost for free' would
> require using streams when working with collections and files, along with
> refactoring important pieces of existing code to do the same.
> > 'Java 8 In Action' is a really great book to get up to speed on the new
> features.
> > From: Pei Chen <ch...@apache.org>
> > To: "dev@ctakes.apache.org" <de...@ctakes.apache.org>
> > Sent: Wednesday, September 16, 2015 2:00 PM
> > Subject: Re: CTAKES-377 : Upgrade to Java 8
> >
> > +1 upgrading to Java 8; been using it unofficially locally.
> >
> >
> >
> > On Wed, Sep 16, 2015 at 1:37 PM, Finan, Sean
> > <Se...@childrens.harvard.edu> wrote:
> >> Can anybody out there think of a reason why we shouldn't upgrade to
> Java 8? Please comment on Jira.
> >>
> >> https://issues.apache.org/jira/browse/CTAKES-377
> >>
> >> Thanks,
> >> Sean
> >
> >
>
Re: CTAKES-377 : Upgrade to Java 8
Posted by Jay Vyas <ja...@gmail.com>.
+1 for sure
> On Sep 18, 2015, at 10:06 AM, Ted Strall <ts...@yahoo.com.INVALID> wrote:
>
> Going to Java 8 can provide a lot of benefit to an application like cTAKES.
> The new features added to Java 8 are a game changer in terms of doing data pipelining. The streams functionality and the ability to do functional programming gives you the opportunity get 'parallelism almost for free.'
> That means the jvm can use all the available cpu cores without the need to explicitly write multi-threaded code, as long as you write functional style code (which basically means no shared variables.) This style of writing code would also make it easier to transition to a distributed processing environment like Spark or Hadoop.
> Of course, to get the benefit of 'parallelism almost for free' would require using streams when working with collections and files, along with refactoring important pieces of existing code to do the same.
> 'Java 8 In Action' is a really great book to get up to speed on the new features.
> From: Pei Chen <ch...@apache.org>
> To: "dev@ctakes.apache.org" <de...@ctakes.apache.org>
> Sent: Wednesday, September 16, 2015 2:00 PM
> Subject: Re: CTAKES-377 : Upgrade to Java 8
>
> +1 upgrading to Java 8; been using it unofficially locally.
>
>
>
> On Wed, Sep 16, 2015 at 1:37 PM, Finan, Sean
> <Se...@childrens.harvard.edu> wrote:
>> Can anybody out there think of a reason why we shouldn't upgrade to Java 8? Please comment on Jira.
>>
>> https://issues.apache.org/jira/browse/CTAKES-377
>>
>> Thanks,
>> Sean
>
>
Re: CTAKES-377 : Upgrade to Java 8
Posted by Ted Strall <ts...@yahoo.com.INVALID>.
Going to Java 8 can provide a lot of benefit to an application like cTAKES.
The new features added to Java 8 are a game changer in terms of doing data pipelining. The streams functionality and the ability to do functional programming gives you the opportunity get 'parallelism almost for free.'
That means the jvm can use all the available cpu cores without the need to explicitly write multi-threaded code, as long as you write functional style code (which basically means no shared variables.) This style of writing code would also make it easier to transition to a distributed processing environment like Spark or Hadoop.
Of course, to get the benefit of 'parallelism almost for free' would require using streams when working with collections and files, along with refactoring important pieces of existing code to do the same.
'Java 8 In Action' is a really great book to get up to speed on the new features.
From: Pei Chen <ch...@apache.org>
To: "dev@ctakes.apache.org" <de...@ctakes.apache.org>
Sent: Wednesday, September 16, 2015 2:00 PM
Subject: Re: CTAKES-377 : Upgrade to Java 8
+1 upgrading to Java 8; been using it unofficially locally.
On Wed, Sep 16, 2015 at 1:37 PM, Finan, Sean
<Se...@childrens.harvard.edu> wrote:
> Can anybody out there think of a reason why we shouldn't upgrade to Java 8? Please comment on Jira.
>
> https://issues.apache.org/jira/browse/CTAKES-377
>
> Thanks,
> Sean
>
>
Re: CTAKES-377 : Upgrade to Java 8
Posted by "Miller, Timothy" <Ti...@childrens.harvard.edu>.
+1 too -- just a note -- looks like the newest version of clearnlp uses java 8 and cleartk is currently considering upgrading to java 8 as well. It will be a necessity soon just so our dependencies work.
Tim
________________________________________
From: Pei Chen <ch...@apache.org>
Sent: Wednesday, September 16, 2015 3:00 PM
To: dev@ctakes.apache.org
Subject: Re: CTAKES-377 : Upgrade to Java 8
+1 upgrading to Java 8; been using it unofficially locally.
On Wed, Sep 16, 2015 at 1:37 PM, Finan, Sean
<Se...@childrens.harvard.edu> wrote:
> Can anybody out there think of a reason why we shouldn't upgrade to Java 8? Please comment on Jira.
>
> https://urldefense.proofpoint.com/v2/url?u=https-3A__issues.apache.org_jira_browse_CTAKES-2D377&d=BQIBaQ&c=qS4goWBT7poplM69zy_3xhKwEW14JZMSdioCoppxeFU&r=Heup-IbsIg9Q1TPOylpP9FE4GTK-OqdTDRRNQXipowRLRjx0ibQrHEo8uYx6674h&m=mTon_uy0qoV5D0aTW5br36j0uzIDQNkSSGMvopiXPzc&s=rde0QR5Gj85wY99Z_PIvwcprvnDUQHmlQxoy8Z9mLAU&e=
>
> Thanks,
> Sean
>
>
Re: CTAKES-377 : Upgrade to Java 8
Posted by Pei Chen <ch...@apache.org>.
+1 upgrading to Java 8; been using it unofficially locally.
On Wed, Sep 16, 2015 at 1:37 PM, Finan, Sean
<Se...@childrens.harvard.edu> wrote:
> Can anybody out there think of a reason why we shouldn't upgrade to Java 8? Please comment on Jira.
>
> https://issues.apache.org/jira/browse/CTAKES-377
>
> Thanks,
> Sean
>
>