Scripting API for everyone
by Dejan Bosanac
I definitely think that dynamic languages for Java platform is an important topic. In that context, a Scripting API as a standardized scripting framework has its own role for Java developers. It is definitely a good thing it is included in JDK 6, but the lack of proper support for earlier JDK's, in my opinion, slows down its wider adoption.
Why is this important? On one side, there are developers that work on "in-house" applications and solutions. Although it may seem that JDK (or JRE) upgrade process in such environments is not a big deal, it is usually a process that is pretty inertial. Many arguments are used in discussions, from compatibility issues and testing needs to "don't fix it if it ain't broken", but also the inertia factor could be often associated to plain laziness.
On other side, you have developers of Java libraries and general-purpose Java applications who try to have user base as wide as possible. In that manner, they usually keep their products either compatible with JDK 1.4 or provide a special "retrotranslated" version of it.
So, it is not hard to see why general scripting support (through JDK 6 exclusive Scripting API) in applications and libraries is not something that we can see on regular basis in Java projects today (especially when there is no official JDK 6 release for OS X yet).
|An off the topic question: I've looked to https://scripting.dev.java.net and noticed, there is no java interpreter for the language i'm using. Maybe i should start a project and build and interpreter for this language. Where should i begin to read? How easy is such a task?|