Re: quick startup time: also consider GroovyServ[1]. It pre-dates the gradle daemon, but is a similar concept some folks might be familiar with.
Re: Bundling a JVM: it is certainly doable but we'd likely do that in the broader community outside ASF unless someone else solves the GPL licensing issue on most JVM artifacts. Re: GraalVM: that is something we want to make easier for Groovy 4 but in the first instance tackling a subset of Groovy (e.g. CompileStatic code) rather than the arbitrary scripts I'd envisage for scripting. Re: Groovy for OS scripting: this has certainly been an area which Groovy has historically excelled in compared to other JVM alternatives. There is no doubt scope for improving things though. It might pay to see if there is anything we can learn from initiatives like JBang[2] which seem very active recently. Cheers, Paul. [1] https://kobo.github.io/groovyserv/ [2] https://github.com/jbangdev/jbang On Thu, Aug 6, 2020 at 1:04 AM MG <mg...@arscreat.com> wrote: > In my opinion the reason why Bash-Script/Perl/Python are the predominant > Linux script languages is, because all or most of them come preinstalled on > every Linux distribution, and because they run standalone with minimal > startup time and memory fotprint. > One of the great things about Grooy is, that it is "one language for > everything", and as a dynamic language with a concise and C-based (i.e. > widely used/understood) syntax, good File support, String interpolation and > powerful closures, it is well suited to be used as a modern Script > language. > > However Groovy is dependent on an existing Java installation (of the > correct version). > > Since JVM based applications are, in my experience, often massively > disliked by people outside of the JVM community (e.g. sys admins), I have > been wondering whether Groovy could/should supply a precompiled, memory > footprint optimized, standalone version that runs without a JVM, so that it > could be used for Linux (Windows) scripting the same as > Bash-Script/Perl/Python are, and if GraalVM could be the principal way to > do it (https://www.graalvm.org/docs/reference-manual/native-image/) > <https://www.graalvm.org/docs/reference-manual/native-image/> ? > > Thoughts ? > mg > > > >
