2009/10/30 Daniel Honig <
daniel.honig@...>:
> > > Good point. While using Groovy for these command line tasks does make
> > > sense in terms of 'eating or own dog food' using a different scripting
> > > language like Python or Ruby for anything that doesn't require the JVM
> > > like pure code generation tasks, certainly would have its benefits in
> > > terms of speed.
> >
> > There more I think about that ... Why not ship Grails with additional
> > - let's say Python - scripts for the more frequently used scripts
> > (i.e. code generation tasks)?
> > The Groovy ones could still be default but impatient users could set
> > some config value to use the Python alternatives in order to gain some
> > extra speed. This would also eliminate the need to ship an additional
> > installer with Grails since a user who deliberately sets that config
> > value is supposed to know what she's doing.
>
> I think the core of the project should it eats own groovy dog food.
> However I think it could be an attractive alternative system. Would love
> to hear how well it works if someone experiments. I think you will still be
> limited by the JVM in places.
Right, that's why I suggested limiting such an alternative system to
thinks like create-domain-class, create-service and so on, which
clearly do not require a JVM as they are simple file system and text
generation tasks.
So, anybody would like to participate in such a project?
--
Viele Grüße / Best regards,
Björn Wilmsmann
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
