It's amazingly helpful on the PI!
Starting a Groovy "Hello, World" on the PI takes like 15 seconds which can be pretty darn irritating, with groovyserv it runs almost instantly.
I had a couple requests though that are quite important for this environment.
1) The timeout is just a few seconds less than the PI takes to spin up Groovy. It would be nice if the value could be increased a touch or made into a parameter.
2) A build for the ARM would be quite helpful. I was able to do it but building GO (Which also doesn't have a PI build) takes the better part of an hour.
3) It would be generally nice to have a way to detect if the server was running. I'm going to try to come up with a way to see if that port is open myself, but a command switch to test it and return a true/false to the CLI would be nice (I could implement #1 myself if I had this).
4) Is there a way to launch Java apps in this jvm too? Can I pass in the name of a JAR or class file instead of a groovy script? This is mostly because of the limited memory on the PI
At any rate, thanks. You've changed groovy from completely unusable to a pretty nice scripting language for that environment.