Google Web Toolkit

Got an e-mail from Lonnie this afternoon pointing out Google’s latest creation: Google Web Toolkit. The is interesting: write all of your JavaScript code as Java first, to take advantage of all of the tools available for Java, then convert it to JavaScript as the final step for deployment.

I think it’s an intriguing concept, but not so sure how I feel about being kept so far away from the JavaScript layer. Am I to assume that the Google Web Toolkit is going to be constantly and consistently updated to provide for all the different browser quirks? Putting too many layers of abstract between me and my JavaScript always makes me nervous. If you’re not familiar with the final outputted code, how can you debug it when something fails? I think the jury is out on this development; let’s see if it gets any traction.

Comments

  1. Steve

    Check out Script# (prototype) as well.

    http://www.nikhilk.net/Scri...

  2. Nicholas C. Zakas

    Wow, very cool! I'm still not sold on this being the future of JavaScript development, but it certainly opens up some cool possibilities.

Understanding JavaScript Promises E-book Cover

Demystify JavaScript promises with the e-book that explains not just concepts, but also real-world uses of promises.

Download the Free E-book!

The community edition of Understanding JavaScript Promises is a free download that arrives in minutes.