Comments on: JavaScript terror alert http://pathfindersoftware.com/2007/11/javascript-terr/ The Fastest Way to Launch Successful Software Thu, 19 Jan 2012 16:36:03 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Heather Fox http://pathfindersoftware.com/2007/11/javascript-terr/#comment-7335 Heather Fox Tue, 20 Nov 2007 19:04:34 +0000 http://www.pathf.com/blogs/?p=194#comment-7335 <p>I can't speak as a developer, but am helping to organize a GWT conference that Pearson will soon host in San Fran, and we've made available some GWT learning materials in advance of the show:<br /> -- GWT co-creators, Bruce Johnson and Joel Webber, did podcast interviews with a Pearson exec editor and provide some interesting tidbits about the GWT development process<br /> -- we assembled a free 300-page eBook that covers topics including GWT Apps, Ajax Security, Scripting in Java and the Eclipse Web Tools Platform. Both of these items are available on the conference home page <a href="http://www.voicesthatmatter.com/gwt2007/." rel="nofollow">http://www.voicesthatmatter.com/gwt2007/.</a><br /> (GWT eBook requires an email address).</p> I can’t speak as a developer, but am helping to organize a GWT conference that Pearson will soon host in San Fran, and we’ve made available some GWT learning materials in advance of the show:
– GWT co-creators, Bruce Johnson and Joel Webber, did podcast interviews with a Pearson exec editor and provide some interesting tidbits about the GWT development process
– we assembled a free 300-page eBook that covers topics including GWT Apps, Ajax Security, Scripting in Java and the Eclipse Web Tools Platform. Both of these items are available on the conference home page http://www.voicesthatmatter.com/gwt2007/.
(GWT eBook requires an email address).

]]> By: Justin Makeig http://pathfindersoftware.com/2007/11/javascript-terr/#comment-7334 Justin Makeig Tue, 20 Nov 2007 16:20:03 +0000 http://www.pathf.com/blogs/?p=194#comment-7334 <p>I had been an intial skeptic of compiling Java to JavaScript. However, as I read more it sounded like GWT would be a good option for getting Java developers immediately productive on UI projects. <br /> In practice, though, I think GWT falls pretty short of that goal. </p> <p>Like most RPC-over-HTTP frameworks, GWT eschews HTTP in favor of its tightly coupled one-off Java serialization tunneled through POST requests. Becuase it only supports a sub-set of Java 1.4 (lang, util, collections, etc.) on the client, we've had to replace our old XML/JSON serialization with GWT-compatible wrappers to our public domain objects, a task I was hoping to avoid. On the plus side, the RPC seems to be very fast and it's nice to work in domain objects on the client.</p> <p>Like its reomting infrastructure, its UI framework and widgets seem to disregard all of the work that's been done over the last 15 years. It gives the impression that the DOM, HTML, and CSS are things to be avoided and completely encapsulated in (ultimately leaky) higher-level interfaces. Its cross-platform solution to complex layouts: nested tables. I still can't figure out how to use its DOM API (curiously implemented as static methods on the DOM class) to set an element's ID attribute/property. What about a CSS selector API? Or even something as simple as element.hasClassName?<br /> The built-in widgets aren't nearly as well thought-out or complete as Ext, Dojo, Moo Tools, etc. and to do anything beyond trivial widget compsoition, you'll have to get your hands dirty with—you guessed it—CSS, HTML, and the DOM.</p> <p>Overall, it might be good tool for rough prototypes or quick and dirty apps, but I'm not convinced of its utility beyond that.</p> <p>I'd be very interested in hear opposing views. Have I missed something fundamental with GWT?</p> I had been an intial skeptic of compiling Java to JavaScript. However, as I read more it sounded like GWT would be a good option for getting Java developers immediately productive on UI projects.
In practice, though, I think GWT falls pretty short of that goal.

Like most RPC-over-HTTP frameworks, GWT eschews HTTP in favor of its tightly coupled one-off Java serialization tunneled through POST requests. Becuase it only supports a sub-set of Java 1.4 (lang, util, collections, etc.) on the client, we’ve had to replace our old XML/JSON serialization with GWT-compatible wrappers to our public domain objects, a task I was hoping to avoid. On the plus side, the RPC seems to be very fast and it’s nice to work in domain objects on the client.

Like its reomting infrastructure, its UI framework and widgets seem to disregard all of the work that’s been done over the last 15 years. It gives the impression that the DOM, HTML, and CSS are things to be avoided and completely encapsulated in (ultimately leaky) higher-level interfaces. Its cross-platform solution to complex layouts: nested tables. I still can’t figure out how to use its DOM API (curiously implemented as static methods on the DOM class) to set an element’s ID attribute/property. What about a CSS selector API? Or even something as simple as element.hasClassName?
The built-in widgets aren’t nearly as well thought-out or complete as Ext, Dojo, Moo Tools, etc. and to do anything beyond trivial widget compsoition, you’ll have to get your hands dirty with—you guessed it—CSS, HTML, and the DOM.

Overall, it might be good tool for rough prototypes or quick and dirty apps, but I’m not convinced of its utility beyond that.

I’d be very interested in hear opposing views. Have I missed something fundamental with GWT?

]]>