From: Jochen T. <bla...@gm...> - 2010-12-29 21:22:19
|
Hi all, I am heavily involved with the Groovy programming language project and I was wondering what it would need to have it in the tool-chain. Groovy mostly compiles to bytecode as java, so that part is not really the problem actually. The problem comes if you want a bit of performance and not a several MB big lib I guess. For me of interest is the .Net target, the javascript target and of course being able to run Groovy on Android. There has been a project enabling Groovy on Android, but it was extremely slow. bye blackdrag -- Jochen "blackdrag" Theodorou The Groovy Project Tech Lead http://blackdragsview.blogspot.com/ For Groovy programming sources visit http://groovy.codehaus.org |
From: Sascha H. <sa...@xm...> - 2010-12-29 22:08:35
|
Hi Jochen, as Groovy is producing class files which contain regular Java Bytecode, there shouldn't be any issue to process applications developed using Groovy with XMLVM. I haven't tried that myself yet though. At the moment we don't have anybody working actively on the .NET target as far as I know, but some people will be spending some time on Win7 mobile. So you might be able to profit from that directly. As for Groovy Apps on Android: it seems to me that all you need to do is run the Groovy-generated class files through the DEX compiler, no? // Sascha On Wed, Dec 29, 2010 at 10:21 PM, Jochen Theodorou <bla...@gm...>wrote: > Hi all, > > I am heavily involved with the Groovy programming language project and I > was wondering what it would need to have it in the tool-chain. > > Groovy mostly compiles to bytecode as java, so that part is not really > the problem actually. The problem comes if you want a bit of performance > and not a several MB big lib I guess. > > For me of interest is the .Net target, the javascript target and of > course being able to run Groovy on Android. There has been a project > enabling Groovy on Android, but it was extremely slow. > > bye blackdrag > > -- > Jochen "blackdrag" Theodorou > The Groovy Project Tech Lead > http://blackdragsview.blogspot.com/ > For Groovy programming sources visit http://groovy.codehaus.org > > > > ------------------------------------------------------------------------------ > Learn how Oracle Real Application Clusters (RAC) One Node allows customers > to consolidate database storage, standardize their database environment, > and, > should the need arise, upgrade to a full multi-node Oracle RAC database > without downtime or disruption > http://p.sf.net/sfu/oracle-sfdevnl > _______________________________________________ > xmlvm-users mailing list > xml...@li... > https://lists.sourceforge.net/lists/listinfo/xmlvm-users > |
From: Jochen T. <bla...@gm...> - 2010-12-29 22:44:53
|
Sascha Haeberling wrote: > Hi Jochen, > > as Groovy is producing class files which contain regular Java Bytecode, > there shouldn't be any issue to process applications developed using > Groovy with XMLVM. I haven't tried that myself yet though. the problem is that a rather big groovy-core lib is about 5MB big. We are planing to split it up though. [...] > As for Groovy Apps on Android: it seems to me that all you need to do is > run the Groovy-generated class files through the DEX compiler, no? Oh that works of course. Only that Groovy is so slow, that it is unusable there bye blackdrag -- Jochen "blackdrag" Theodorou The Groovy Project Tech Lead http://blackdragsview.blogspot.com/ For Groovy programming sources visit http://groovy.codehaus.org |
From: Sascha H. <sa...@xm...> - 2010-12-29 22:53:15
|
On Wed, Dec 29, 2010 at 11:44 PM, Jochen Theodorou <bla...@gm...>wrote: > Sascha Haeberling wrote: > >> Hi Jochen, >> >> as Groovy is producing class files which contain regular Java Bytecode, >> there shouldn't be any issue to process applications developed using Groovy >> with XMLVM. I haven't tried that myself yet though. >> > > the problem is that a rather big groovy-core lib is about 5MB big. We are > planing to split it up though. > I see! Well, we are currently doing a lot of work in the area of dependency analysis for the C output. We just analyzed parts of the JDK ad selected an interesting sub-set. In addition we do a very naive dependency analysis, which further reduces the classes that are pulled in for a given application. Might be worth a try at some point. > > [...] > > As for Groovy Apps on Android: it seems to me that all you need to do is >> run the Groovy-generated class files through the DEX compiler, no? >> > > Oh that works of course. Only that Groovy is so slow, that it is unusable > there Oh, so you mean the groovy classes that are compiled to DEX are too slow? > > > bye blackdrag > > -- > Jochen "blackdrag" Theodorou > The Groovy Project Tech Lead > http://blackdragsview.blogspot.com/ > For Groovy programming sources visit http://groovy.codehaus.org > > |
From: Jochen T. <bla...@gm...> - 2010-12-29 23:13:58
|
Sascha Haeberling wrote: [...] > As for Groovy Apps on Android: it seems to me that all you need > to do is run the Groovy-generated class files through the DEX > compiler, no? > > > Oh that works of course. Only that Groovy is so slow, that it is > unusable there > > > Oh, so you mean the groovy classes that are compiled to DEX are too slow? the startup time is the first problem, the general speed the second. While the JVM can Groovy to a reasonable speed, most of the things we use for that are not available there. for example we cannot use runtime generated classes... or am I wrong? Without them we really on pure reflection, and reflection is not known to be fast. bye blackdrag -- Jochen "blackdrag" Theodorou The Groovy Project Tech Lead http://blackdragsview.blogspot.com/ For Groovy programming sources visit http://groovy.codehaus.org |