Though that'd also require someone coming along and building a great IDE for stab.
As far as writing Javascript apps in JRuby/Clojure via GWT...why use GWT? It's so heavily focused on Java/static type analysis, I'd think you'd be able to make a better/easier Ruby->Javascript translation by just starting anew.
The JRuby runtime itself uses reflection/some-day-invokedynamic to shoehorn a dynamic language into a static VM. Besides the fact the JRuby runtime would never get through GWT's no-reflection/nothing-fancy compiler, you're going from ruby dynamic semantics -> Java static semantics -> Javascript dynamic semantics.
Seems simpler to skip the static part. Some sort of Ruby's meta class semantics implemented via Javascript's prototype semantics.
I imagine the same thing applies with clojure, but I don't know as much about it.
Given it's much closer to Java (no new type system, etc.), I think it'd actually be easier to get stab/GWT integration:
http://code.google.com/p/stab-language/
Though that'd also require someone coming along and building a great IDE for stab.
As far as writing Javascript apps in JRuby/Clojure via GWT...why use GWT? It's so heavily focused on Java/static type analysis, I'd think you'd be able to make a better/easier Ruby->Javascript translation by just starting anew.
The JRuby runtime itself uses reflection/some-day-invokedynamic to shoehorn a dynamic language into a static VM. Besides the fact the JRuby runtime would never get through GWT's no-reflection/nothing-fancy compiler, you're going from ruby dynamic semantics -> Java static semantics -> Javascript dynamic semantics.
Seems simpler to skip the static part. Some sort of Ruby's meta class semantics implemented via Javascript's prototype semantics.
I imagine the same thing applies with clojure, but I don't know as much about it.