Recently while cursing the slowness of GWT compilation, the slowness in the browser, and the lack of Java 6 features, it occurred to me that if GWT had simply been built on top of the Java Applet technology it could really overcome these limitations.
Does anyone know why GWT wouldn't be much better if it were java bytecode running in an applet? All the major browsers support applets, the Java VM runs the code nice and fast, and applets have decent access to the DOM and the ability to run javascript. Everything that is needed to implement GWT is available to an applet, as far as I can tell. Thoughts? If I had time I'd experiment and try making a knock-off of GWT using a hidden applet so I could just write every in Java, run and debug it in the Java VM ... could even use Java's built-in RPC mechanism if I wanted to. Interesting concept, although it's likely I'm missing something important about why the GWT team didn't go this route in the first place. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~----------~----~----~----~------~----~------~--~---
