Why did you found OpenAjax?
If you go back nine months, the key problem that folks were having was, one, What exactly is the definition of AJAX? The second [problem was], How do you get [a] message out to all parties that would be cross-vendor? The third thing was, From a technology standpoint, how can you basically start looking at what was going to happen when looking across toolkits?
So [those were] the reasons why we started OpenAjax. Now, when you start looking at the bigger picture here and at what IBM is doing in this space, [you'll see that it] is in parallel to starting OpenAjax; what we did [at IBM] is, we started a project inside IBM to work on trying to bring down the level of complexity of writing and debugging applications, AJAX applications in particular. And the way we did it was, we built a piece of code called the AJAX Tooling Framework which went on top of Eclipse, which is the core foundation for tooling that we are using, and we can demo the AJAX Tooling Framework with the whole idea behind it [being] to bring down that level of not only complexity but also to allow someone to write a lot more AJAX code in a much shorter amount of time and get it published faster.
What about Microsoft -- which has its AJAX technology, Atlas -- not being a part of OpenAjax? Are there any more overtures being made? Are they just going to sit on the sidelines like they seem to do with other industry initiatives, like Eclipse? What's going on there with Microsoft?
I actually just spoke with Microsoft yesterday about joining OpenAjax, and they've taken back the details and are thinking about it, and they'll get back to us.