[I realize this is a bit OT because we were targeting desktop
scripting, but given the javascript solution, drifting into the "web"
with both client and server side programming, I thought it would be OK
to diverge a bit.]
Well, if the Browser is the Computer, one of the issues I've run into
is multiple languages: one on the server, and another on the browser.
Java was popular because you could use the same language on both
sides: servlets and applets.
But there is yet another javascript rebirth going on: server-side
javascript. John Guerin pointed this out to Steve and me while we
were working with the Google App Engine, and I was kvetching about
having to deal with javascript in the client (google maps, primarily)
and python/django on the server.
Jaxer is the critter that pulls off this magic.
http://www.aptana.com/jaxer
http://ejohn.org/blog/server-side-javascript-with-jaxer/
I've never liked most of the server-side solutions, they were just too
ugly. Php for example was really designed as a "web shell", not a
full featured language (IMHO). But Javascript is a nifty enough
language that having on both sides of the wire is compelling.
And Aptana is another alternative to Google App Engine and Amazon EC2,
and considerably cheaper than the latter.
I haven't used it yet, so would love to hear of other folks'
experience with jaxer and server-side javascript.
-- Owen
============================================================
FRIAM Applied Complexity Group listserv
Meets Fridays 9a-11:30 at cafe at St. John's College
lectures, archives, unsubscribe, maps at http://www.friam.org
