You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@groovy.apache.org by Jochen Theodorou <bl...@gmx.org> on 2017/09/04 19:09:34 UTC
Groovy using Graal
Hi all,
since Graal is now available in JDK9 by default I was wondering if we
should go into a path for deep integration with Graal if we can take
advantage of it.
In the past I was quite partial to this because of the licensing of
Graal itself. I know from before it was GPL with or without classpath
extension. But even with classpath extension I was not feeling well
about depending on it and the trouble users would have go through to
setup an optional Graal part.
Well, now since it is part of JDK9 those troubles are of the past. Now
everyone has a ready to use Graal afaik. And we do no longer have to
distribute it. That means we can consider really depending on it, like
we depend on the Java platform itself.
How do others think?
bye Jochen
Re: Groovy using Graal
Posted by Guillaume Laforge <gl...@gmail.com>.
Code name: Graavy :-D
On Tue, Sep 5, 2017 at 10:46 AM, Russel Winder <ru...@winder.org.uk> wrote:
> On Tue, 2017-09-05 at 10:44 +1000, Paul King wrote:
> > Sounds like it might be useful for Groovy 4+.
> >
>
> If the plan is for Groovy 3 to depend on JDK8 and Groovy 4 to depend on
> JDK9 then yes. However is there a need to be quite so conservative?
> Groovy has so often had "hacks" so a version of Groovy could make use
> of more recent JDKs and yet still work on "long past end of life"
> versions of JDK. In this vein Groovy 3 could have a JDK9 variant using
> Graal. This option would, I feel, be a good marketing line for Groovy.
> "Graal Groovy now not later."
>
> --
> Russel.
> ============================================================
> =================
> Dr Russel Winder t: +44 20 7585 2200 voip:
> sip:russel.winder@ekiga.net
> 41 Buckmaster Road m: +44 7770 465 077 xmpp: russel@winder.org.uk
> London SW11 1EN, UK w: www.russel.org.uk skype: russel_winder
--
Guillaume Laforge
Apache Groovy committer & PMC Vice-President
Developer Advocate @ Google Cloud Platform
Blog: http://glaforge.appspot.com/
Social: @glaforge <http://twitter.com/glaforge> / Google+
<https://plus.google.com/u/0/114130972232398734985/posts>
Re: Groovy using Graal
Posted by Russel Winder <ru...@winder.org.uk>.
On Tue, 2017-09-05 at 10:44 +1000, Paul King wrote:
> Sounds like it might be useful for Groovy 4+.
>
If the plan is for Groovy 3 to depend on JDK8 and Groovy 4 to depend on
JDK9 then yes. However is there a need to be quite so conservative?
Groovy has so often had "hacks" so a version of Groovy could make use
of more recent JDKs and yet still work on "long past end of life"
versions of JDK. In this vein Groovy 3 could have a JDK9 variant using
Graal. This option would, I feel, be a good marketing line for Groovy.
"Graal Groovy now not later."
--
Russel.
=============================================================================
Dr Russel Winder t: +44 20 7585 2200 voip: sip:russel.winder@ekiga.net
41 Buckmaster Road m: +44 7770 465 077 xmpp: russel@winder.org.uk
London SW11 1EN, UK w: www.russel.org.uk skype: russel_winder
Re: Groovy using Graal
Posted by Paolo Di Tommaso <pa...@gmail.com>.
I've seen some presentations and Graal looks impressive. It seems Oracle is
investing a lot on it, already having other languages running on it.
IMO Groovy would be benefit a lot being able to run on Graal.
p
On Tue, Sep 5, 2017 at 2:44 AM, Paul King <pa...@asert.com.au> wrote:
> Sounds like it might be useful for Groovy 4+.
>
>
> On 5 Sep. 2017 5:09 am, "Jochen Theodorou" <bl...@gmx.org> wrote:
>
>> Hi all,
>>
>> since Graal is now available in JDK9 by default I was wondering if we
>> should go into a path for deep integration with Graal if we can take
>> advantage of it.
>>
>> In the past I was quite partial to this because of the licensing of Graal
>> itself. I know from before it was GPL with or without classpath extension.
>> But even with classpath extension I was not feeling well about depending on
>> it and the trouble users would have go through to setup an optional Graal
>> part.
>>
>> Well, now since it is part of JDK9 those troubles are of the past. Now
>> everyone has a ready to use Graal afaik. And we do no longer have to
>> distribute it. That means we can consider really depending on it, like we
>> depend on the Java platform itself.
>>
>> How do others think?
>>
>> bye Jochen
>>
>
Re: Groovy using Graal
Posted by Paul King <pa...@asert.com.au>.
Sounds like it might be useful for Groovy 4+.
On 5 Sep. 2017 5:09 am, "Jochen Theodorou" <bl...@gmx.org> wrote:
> Hi all,
>
> since Graal is now available in JDK9 by default I was wondering if we
> should go into a path for deep integration with Graal if we can take
> advantage of it.
>
> In the past I was quite partial to this because of the licensing of Graal
> itself. I know from before it was GPL with or without classpath extension.
> But even with classpath extension I was not feeling well about depending on
> it and the trouble users would have go through to setup an optional Graal
> part.
>
> Well, now since it is part of JDK9 those troubles are of the past. Now
> everyone has a ready to use Graal afaik. And we do no longer have to
> distribute it. That means we can consider really depending on it, like we
> depend on the Java platform itself.
>
> How do others think?
>
> bye Jochen
>
Re: Groovy using Graal
Posted by Daniel Sun <re...@hotmail.com>.
Hi Jochen,
Graal[1] looks amazing, +1 for leveraging its power.
Cheers,
Daniel.Sun
[1]
http://www.oracle.com/technetwork/oracle-labs/program-languages/overview/index.html
--
Sent from: http://groovy.329449.n5.nabble.com/Groovy-Dev-f372993.html