When I first saw the news about the newly released Google’s Web Toolkit:
I thought to myself, since when is Google so into Java anyway? Friends of mine know that I’ve never been a big fan of Java mainly due to its There’s Only One Way To Do It philosophy that so starkly contrasts the motto of my favourite language – Perl. As much as I try to avoid it, I often find myself needing to use it (with non-trivial involvement) throughout the years (10!) Even in my current job at NeuStar, I would say Java has 80% mindshare in the company. These days, with advanced tools like Eclipse (not to mention age – mine, that is), my view on the language has certainly improved by heaps and bounds.
Until now, I’ve been wary about going Ajax with anything I program mainly because I have to learn about browser quirks and inject ugly hacks. Moreover, it will invariably reverse the 80-20 rule; unless you are Ajax God, you will spend 80% of your time achieving 20% core functionality.
So, this is very good news and gives me the reason to incorporate some snazzy Ajax in my existing apps wherever it makes sense. Once I get some spare cycles, this will be the first I play with.