The qooxdoo framework recently released its 1.0 version.  I remember first looking at qooxdoo back in 2007 when evaluating JS frameworks for a company I was working at.  qooxdoo was a bit of a ‘dark horse’ at the time – we ultimately decided on YUI at that point, largely because of the documentation available for YUI (had considered jQuery and others as well).

There seems to have been a huge improvement in qooxdoo in the intervening years, and the framework now boasts an impressive array of features, including a build system, compression, integrated unit testing, internationalization, robust GUI toolkit and more.  However, it’s 2009 (almost 2010) and many competing frameworks offer a similar set of features with varying levels of support, so how does qooxdoo gain traction?

The ease with which people can adopt your system and use it to fit their small needs first is (imo) a likely indicator of how much traction a project can gain, and qooxdoo seems to be doing their fair share of making things easy on developers.  The most interesting to me is their playground, which gives developers a way to test out qooxdoo code by using provided sample code and editing and running the code, all from the browser – no installation required.  Give it a try!  A combination of tutorials, ‘getting started’ and a browseable API all will go a long way towards helping developers get a handle on what qooxdoo has to offer.

Congrats to the qooxdoo team on your 1.0 release!