Rodney Gedda's review provided a fair and balanced analysis of some of the features of once:radix.

The issue of configuring the browser is due to the lock-down of some features in Firefox. But to make some once:radix functions available (e.g. file uploads) signed.applets.codebase_principal_support must be enabled. Alternatively, an SSL signed certificate (e.g. from Verisign) is needed. Both solutions are simple and a matter of choice when developing an application.

The need to delete Rodney's prefs.js file is a problem that occurs infrequently. In fact, it is only the second time I have seen the need to do it, in the many thousands of installations performed. But then, in accordance with Murphy's Law, software is most likely to go wrong during an important product review!

Cross browser support is an important issue. At our last attempt, Internet Explorer was 16 times slower than Firefox 2. With the speed improvements achieved in Firefox 3, the difference would be even more dramatic.

We face the same issues with browser compatibility as other RIA technologies, though it may be more acute with once:radix, due to the sophistication of our client.

We have seen extraordinary changes in all of the associated technologies over the life of this project and expect this will continue. Nevertheless, the rewards far outweigh the small challenges we face. The key platform of our design strategy is to conform to W3C and other standards. If that means, failing to achieve Microsoft compatibility in the short term, so be it. However we are in discussion with Microsoft to develop a strategy to achieve full compatibility without loss of performance. Hopefully, this will be resolved soon.