Thursday, June 29th, 2006p>Andy Clark of Zimbra wrote a letter to the Apache Incubator where he explained why the Kabuki contribution was now withdrawn.
A few of the things we’ve learned:
- Most parties in the OpenAjax initiative believe one sweet spot for AJAX toolkits will be for augmenting existing HTML pages. This is a more evolutionary approach that provides a more generic fallback in terms of accessibility, legacy clients, and so on. So a key constituency is the “HTML design center”, and today we believe Dojo to be a better choice for HTML developers than Kabuki.
We think that Kabuki is an ideal fit for a certain class of Ajax solutions but not for others. As such, we expect Kabuki to co-exist with Dojo, GWT, and others. We now agree with other members of OpenAjax that a peer relationship between these projects is best. We feel that this approach facilitates sharing and collaboration and is better than an approach where one project has a special relationship with Apache while others do not.
Posted by Dion Almaer at 8:09 am