> So I'd search the reason for qooxdoo's less-than-optimal adoption ... IMO, it has nothing to do with SEO, steep learning curve or the like. The learning curve is not steep for someone bringing OOP skills to the table. SEO usually doesn't really matter for real applications. SEO is something for web sites, and qooxdoo was never designed for doing web sites.
IMO, the reason for qooxdoo's slow adoption is the structure of the current market. Real apps with a web interface have taken off only during the last few years. The bulk of the people hired to do them are the people trained on web stuff during the dot com bubble and the Y2K crisis, who are proud masters of CSS and HTML, not of OOP. Qooxdoo will unlikely be ever whole-heartedly adopted by such people - it's quite different from what they know and what they value. But since customers around the world tend to rely on tried and trusted technologies, qooxdoo and qooxdoo-ish frameworks will have a hard time really hitting it off, as long as they are the new kids on the block, whereas jQuery, prototype and the like, even if specifically designed with highly dynamic web sites in mind, and not business apps with a web interface, are perceived as the more conservative, more reliable and less risky approach. This needs time to change, but is IMO an opportunity for qooxdoo. When others will just begin to realize that web apps and dynamic web sites are different animals, needing different tools to build, and think of building something usable for business apps with a web UI, qooxdoo will already be the known, tried and tested solution in the area of web apps. Only, it won't happen overnight. Another reason for qooxdoo's slow adoption might be the strong control of 1&1 over its development. It's not the road traveled by most open source projects. In most successful open source projects, even if there are some core developers, there is an easier mechanism in place to integrate source code from external developers, which then gets maintained by the qooxdoo team/developer community. From what I can tell, this mechanism is less open for qooxdoo than it is for other projects. Committing to a framework on which they feel they have less influence than they have on other open source projects might scare off some larger potential users, for which strategic decisions are not taken easily or light-mindedly. flj ------------------------------------------------------------------------------ ThinkGeek and WIRED's GeekDad team up for the Ultimate GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the lucky parental unit. See the prize list and enter to win: http://p.sf.net/sfu/thinkgeek-promo _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
