Re:a scripting language that targets the java vm !
on
Groovy in Action
·
· Score: 1
You can package a Grails app as a WAR using the
grails war command. The WAR can then be deployed to a servlet container (such as Tomcat) or a JEE server (such as JBoss). Ruby on Rails also supports several mechanisms to avoid per-request startup overhead. (The JRuby people are working on deploying Rails apps as WARs...)
I have tried using Groovy for command line utilities and JVM performance has, in fact, been an issue. There are ways such as Nailgun for elminating JVM startup overhead, but Groovy (last I checked) doesn't provide an "out of box" solution.
Sure stress may cost $300 billion per year in related costs, but the absence of stress would eliminate at least half of the remaining $11,000 billion in U.S. GDP.
Apple had a product in 1988, with the confusing name "MacWorkstation", that let a host application send text messages to a Macintosh and create a rich-client GUI for a mainframe application. If I recall correctly, you would write the event loop in COBOL (as well as other languages) on the server.
It was expensive, didn't have the simplicity of HTML as a starting point and, perhaps, was a little ahead of its time. (Client/Server was still catching on.) The fact that few mainframe guys liked Macs may have been a factor, too.
Links:
"The only problem with the MacworkStation [a software program] is that instead of making it a public domain standard, Apple is licensing the source code for $1500 to 'interested' parties" - MacTech Magazine archived article
Slashdot Mirror
I have tried using Groovy for command line utilities and JVM performance has, in fact, been an issue. There are ways such as Nailgun for elminating JVM startup overhead, but Groovy (last I checked) doesn't provide an "out of box" solution.
Sure stress may cost $300 billion per year in related costs, but the absence of stress would eliminate at least half of the remaining $11,000 billion in U.S. GDP.
It was expensive, didn't have the simplicity of HTML as a starting point and, perhaps, was a little ahead of its time. (Client/Server was still catching on.) The fact that few mainframe guys liked Macs may have been a factor, too.
Links:
"The only problem with the MacworkStation [a software program] is that instead of making it a public domain standard, Apple is licensing the source code for $1500 to 'interested' parties" - MacTech Magazine archived article
Apple Computer History Weblog