Here's what people say about using Netzke in their projects.

At pme Familienservice we are building a rather large RIA with Rails. We quickly agreed that Ext JS is by far the most mature and fully-featured component-framework currently. Soon we faced a constant mess of view helpers and partial trying to wrap Ext's components and we realized we need some component-abstraction on the server-side. When we learned about Netzke, it was love on first sight as it provides exactly what we need. After some initial learning curve and an amazingly prolific month together with the lead developer, we are now very productive with Netzke and already have written about 150 custom components with it - this would have never been possible with our partials-approach. After looking at the competition I am certain that Netzke is the only serious option for component-based frameworks with rails. With components we can now abstract the huge complexities we are facing into easy-to-reason-about components, and we can make use of all common code-reuse patterns like inheritance and composition using Ruby.

Paul Schyska, pme Familienservice

Yes we do [use Netzke in production] for a mid-size backoffice application localized in French, English and Thaï. We started with Netzke 0.6 & ExtJS3 and just finished upgrading to Netzke 0.7 & ExtJS4 (upgrading took 4 days with a little pain sometimes, but all in all it went pretty well). The development time for the application is about ~3 months with 3 junior developpers and me (got 100% test coverage + acceptance testing with Cucumber). I've been investigating before choosing Netzke (JQuery UI, Roll-our-own UI, pure ExtJS, ...) and I'm very happy with the results (the customer too, which is much more important).

We are now happily starting another customer project with Netzke & ExtJS4.

Richard P., www.nuxos.fr