Here is some information on how Joomfish compares to Nooku :
1. Performance: The whole concept of how JF deals with storing translations cause a lot of overhead. A lot of data is constantly being moved around and rewritten. Nooku ‘respects’ the way an application talks to the database, and interferes as little as possible.
2. Ease of use: JF introduces a number technical terms, users have to understand these to be able to work with the system. There are a lot of cryptic configuration options, each of them again requiring you to read the documentation to understand the effect. Nooku introduces no new technical terms, and at the moment has no configuration options. Instead, Nooku makes decisions based on it’s environment, just like a well-informed user would.
3. User interface: JF introduces a user interface where content is translated. Nooku seamlessly integrates with each extension’s existing user interface. Users don’t need to learn a new interface, they can keep there existing workflow.
4. 3PD compatibility: for each extension on your JF site, you need a special configuration file. These have to be located (or developed by the JF team, the extension’s developer or someone skilled), installed and managed. Nooku works out of the box with every extension that is developed according to the joomla standards.
5. General robustness: JF has a bunch of features to deal with orphaned or corrupted data. This is a telltale sign that JF sites often end up actually having corrupted data. For the same reason as in item 1 above, Nooku can’t easily mess up data, because it hardly touches it.
6. To get full SEF support with Joomfish you need to install another third party component like sh404SEF, with Nooku you get fully humanly readable URL’s out of the box.
7. Setup: 2, 3 and 4 and 6 together vastly reduce the time needed to go from zero to up-and-running
What JF doesn’t have:
8. Statistics: Nooku keeps track of what content is added, translated, modified, deleted, in which languages and by whom. This makes it easy for administrators to keep track, tell translators what to do, etc.
9. Access control: Nooku allows administrators to limit the permissions of translators. This protects the content from accidental overwriting. For example, a French translator can only translate existing items to French, but can’t add new ones or edit any other languages.
10. Improves Joomla: Nooku adds a number of features to Joomla that are not strictly translation-related, such as better SEF, and easier ways to manage all different kinds of content in one place.
11. Nooku literaly allows you to translate everything, not only the actual texts you add, but also settings can differ from one language to the other, for example article metadata and parameters.
12. Framework: Nooku comes with Koowa, a rapid application development framework that allows developers to quickly build much more powerful applications than is possible with plain Joomla. Koowa is becoming so powerful, I’m confident that even if JF comes up with a brilliant new feature, we can use Koowa to recreate and improve that feature in Nooku in mere weeks.