Not bugs - exceptions!

The application has matured quite a bit over the past year. Granted there is still a long ways to go. Since the team has adopted Continuous Integration there seems to have been a steep drop in regressions. Be patient, it is still in beta after all.

I think java was a bad decision. Its known to be memory hungry, slow and still has a lot of bugs. QT [ http://en.wikipedia.org/wiki/Qt_(toolkit) ]instead is known to be stable, fast and also available for *nix, win and mac (crossplatform). so why using java? I really don't get it. :(

I've been developing using Qt a lot, so I agree that would have been a good decision. But, Java is not slow as you state - do some benchmarks. Memory wise...yea eat more memory because of garbage collector, but if you not a very good c-programmer, you can get into a lot of problems with memory leaks too. Wualaa-team just seems to need some descent java-programmers. It's not okay to have a beta for a year that crash all the time, no matter what the reason is. Just hire better people!

Here is the conclusion of an Study named "Qt vs. Java - A Comparision of Qt and Java for Large-Scale, Industrial-Strength GUI Development" by Matthias Kalle Dalheimer.

"Conclusion
We have compared the two development platforms Java/AWT/Swing and C++/Qt
regarding their suitability for efficiently developing high-performance, userfriendly
applications with graphical user interfaces. While the Java-based platform
only manages to achieve comparable programmer efficiency to that of the C++/Qt
platform it is clearly inferior when it comes to runtime and memory efficiency.
C++ also benefits from better tools than those available for Java.
When it comes to the GUI libraries, Swing and Qt, the poor runtime-efficiency of
Java programs is clearly evident, making the Java/Swing platform unsuitable for
many GUI development efforts, even though the programming experience is
comparable. Since Qt does not enforce particular programming paradigms as Swing
does with the Model-View-Controller paradigm, Qt programmers often achieve
more concise code.
Both independent academic research and industrial experience demonstrate that the
hype favouring Java is mostly unjustified, and that the C++/Qt combination is
superior. This is mainly due to the runtime and memory efficiency problems in Java
programs (which are especially striking when using the Swing GUI toolkit) and
Java’s failure to deliver increased programmer efficiency. In various programming
projects we have been involved in, junior-level programmers learnt Java faster, but
more experienced and senior-level programmers (which are usually in charge of the
application design and the implementation of the critical parts of an application)
achieved better and faster results using C++.
Java/Swing may be appropriate for certain projects, especially those without GUIs
or with limited GUI functionality. C++/Qt is an overall superior solution,
particularly for GUI applications."

A PDF of the Study can be found here:
http://turing.iimas.unam.mx/~elena/PD...

Also interessting:
http://www.google.com/search?q=java+v... ;)

You didn't read my lines. AWT/Swing is a lot slower an Qt, hands down. But I didn't say anything else. I say, Java - the language itself - is not far behind c++. Me myself implemented a complex algorithm using Trie Trees, Binary search, etc for a huge amount of data (~30MB dictionary) with almost the same benchmarks (slower, but talking tens of milliseconds) as a similar c implementation. ANyway, ending here. The discussion itself was about how alpha the Wuala implementation been for a year with ~0 visible progress.

The majority of changes have been under the hood. Improving efficiency, stability and extendability.

Like IO buffer overflows, and memory buffer overflows? That's pretty much belongs to "under the hood". Stability...eh...are you running the same version as everyone else? Don't add features; fix the ones that are available. Your competitors are catching up. OK, enough said. Notice taken - I hope.