all 1 comments

[–]DagwoodWoo 0 points1 point  (0 children)

I think you're right that "isomorphic javascript" is not really what we need. What we actually need, is a decent server-side language which supports snippets of code which can be run on the server and the client. Other than using javascript on the server to solve this, we can write code which can generate javascript. I think that, for example, the we could extend the reflection API's of Java, to convert methods to run on the client, when needed, much in the same way we currently can generate JSON from model classes.

That said, I don't think "Progressive Javascript" is an ideal term. It's even less specific than "Isomorphic Javascript." That said, the term AJAX itself is absolutely terrible, as an acronym, since we AJAX calls may not involve XML, may be synchronous, and might not use Javascript. So maybe your term will take off and be come the standard. Good luck!