Re:Isomorphic JavaScript: The Future of Web Apps
by esamek on Monday November 11, 2013 @09:08PM
(#6715423)
GWT is not Java on both sides. Its Java on the server, Javascript on the client. The Java client side code compiles to Javascript...the abstraction is way greater than what OP is presenting. (JS & JS)
GWT is/was a terrible amount of overhead baggage, but had some brilliant event systems and DOM tricks for its day.
Re:Isomorphic JavaScript: The Future of Web Apps
by dragonwriter on Monday November 11, 2013 @09:52PM
(#6715558)
> GWT is not Java on both sides. Its Java on the server, Javascript on the client. The Java client side code compiles to Javascript..
And the Java server code compiles to JVM bytecode. Languages often compile to some other form to run, and the fact that the compilation target is different for different parts doesn't change that the programming language is the same.
Re:Isomorphic JavaScript: The Future of Web Apps
by larsmak on Tuesday November 12, 2013 @09:34AM
(#6718004)
> GWT is/was a terrible amount of overhead baggage
GWT is very much alive and kicking, but it's primarily used on internal business applications with large and complex code bases. And what overhead baggage are you talking about? GWT is designed to reduce overhead though cross-compiled, browser-spesific builds, dead-code removal, and js-optimizing.
This is a classic "impedance mismatch" like O/R mapping. At the end of the day, there may be no good, i.e. simple, solution. It is inherently difficult and messy.