« What Should I Buy? Parallels or Fusion? | Main | Starting a High Tech Business: Get a Clubhouse »
Google Web Toolkit
I just posted my interview with Bruce Johnson on the Google Web Toolkit. This was a fun interview and I learned a lot. GWT allows you to write AJAX applications in Java that then gets compiled to Javascript.
Posted by windley on October 23, 2007 8:14 AM
Comment from Jason Etheridge at October 23, 2007 1:41 PM
An excellent discussion: informative and useful, with plenty of insightful questions.
I've been toying with various Javascript libraries (mainly YUI), but Bruce's overview has convinced me that I should take the plunge with GWT. While I'm not a big Java user (C++ and Python being what I'm most used to), the "killer" feature for me is that GWT offers cross-browser through the generated Javascript.
Overall, it really makes so much sense to let a compiler do the work if possible, and with the quirkiness of browser-based Javascript support, GWT does seem to provide real value in keeping the developer from wasting time sorting out such low-level problems. The hosted browser allowing the use of a real debugger is also extremely compelling; Firebug is great, but can only go so far.
While I fail to see the benefit of static typing (I prefer dynamically typed languages, especially as manifested in Python), that won't stop me. :-)
Thanks for arranging such a great discussion!
Comment from Michael Neale at October 23, 2007 4:58 PM
@Jason: yeah, it surprised me too. when I first heard of GWT I thought I would hate it. Java is pretty verbose at the best of times. but I have had nothing but success with GWT. The compiler is white magic, as is the hosted mode + debugging (you can start it up, hack away, make changes on the fly etc).
I suppose with javascript 2 in the future, and some optional typing, you could have a JS to JS compiler with a nice widget API to do something simpler, but for now, GWT works a treat.
The constraints GWT put on you end up making a very responsive app. I have a theory that static typing for rich GUIs is a good idea: as it is hard to test them programmatically, any extra work the compiler can do really saves you a lot of time (even though you have to invest a little more up front keeping the compiler happy).
Leave a comment
I encourage you to leave a comment below. Your email address will not be displayed on Technometria, but allows me to communicate with you directly. Your email address won't be displayed, but will be used to compute a MicroID for your comment.