This morning on Twitter, Rich Sharples, Director of Product Management for the JBoss EAP (Enterprise Application Platform) and former Sun compadre, sent out the news that JBoss was adopting the Google Web Toolkit.
Here is what Rich had to say in his blog a few hours later:
Today Red Hat announced a couple of things :
1. that we’ve signed Google’s corporate contributor agreement
2. that we’re adopting GWT (Google Web Toolkit) as a core part of JBoss Middleware
The world doesn’t need another Java framework for developing rich AJAX apps. so we’ve decided to go with what we think is a real leader – Google Web Toolkit. (Read more)
(I hope this doesn’t mean that JBoss will be replacing us as the self-proclaimed GWT poster child 😉 )
GWT draws inspiration from the Brady Bunch (does that make Alex, Cindy?)
And in other News
In other GWT related news today, Google posted a timeframe and details for their next release, 1.6. And as if that wasn’t enough, Google also posted four sets of developer videos where each of the four gentlemen (including Lombardi Blueprint‘s very own Alex Moffat) discuss how GWT has helped them and why they chose it as their weapon of choice.
Update: This just in… (non-geeks need not read on)
A few hours after I originally posted this entry, the Register posted their summary of today’s events and quoted our Mr. Moffat
Alex Moffat, chief engineer at the business process management firm – and GWT user – Lombardi Software told El Reg he’s mostly interested in GWT 1.6’s string performance and compiler improvements.
However, Moffat said he’s disappointed to see GWT’s in-browser hosted mode has been moved to a “post 1.6” feature on Google’s roadmap. The feature, which lets developers debug their apps within a web browser rather than GWT, was originally slated for version 1.5 and then 1.6 until Google’s latest development update.
Pau for now…