Linked by Thom Holwerda on Fri 20th Feb 2009 15:47 UTC, submitted by Jarle Anfinsen
Qt According to a recent announcement, Nokia/Qt Software has decided to discontinue the development of Qt Jambi after the March 2009 release of version 4.5. Jambi is a Java version of the popular Qt toolkit. The library will be made available under the LGPL license, and Qt Software will host and facilitate a community driven continuation of Jambi.
Thread beginning with comment 350041
To read all comments associated with this story, please click here.
Not unexpected
by danieldk on Fri 20th Feb 2009 19:25 UTC
danieldk
Member since:
2005-11-18

Qt Jambi is very nice, but there did not seem to be much uptake. It's nice that it can be continued as a community project under the LGPL. Some of the other bindings are also community projects, so that should be fine.

Reply Score: 2

RE: Not unexpected
by leos on Fri 20th Feb 2009 20:34 in reply to "Not unexpected"
leos Member since:
2005-09-21

Qt Jambi is very nice, but there did not seem to be much uptake.


I think there was just too much overlap. C++ benefits massively from the complete class library in Qt. Java has their own, and it would be silly to drop it all for Qt. The only use of Qt in Java is to have nicer native GUIs, and that's just not as much of a selling point.

As for the language issue, Java doesn't really give you much over C++/Qt. You lose speed, add overhead, and don't really save anything significant on development time. They've done such a good job getting C++ easier and more productive that it reduces the appeal of higher level languages. I'm currently using PyQt quite a bit, and although it makes some stuff easier, my programs aren't really getting significantly easier or faster to develop. Some things are better in python, but you don't gain a huge amount.

Reply Parent Score: 3

RE[2]: Not unexpected
by danieldk on Fri 20th Feb 2009 22:15 in reply to "RE: Not unexpected"
danieldk Member since:
2005-11-18

As for the language issue, Java doesn't really give you much over C++/Qt.


I fully agree. The primary major advantage of Java (platform-independence) evaporates when you combine it with a native toolkit. Java is stuck in a hard place when it comes to desktop applications. I have seen very few people who actually like Swing. And there is not much reason to use Java plus a native toolkit over C++ with the comfort of Qt (or some other language/toolkit combination). Sun seems to have lost two opportunities: Microsoft closed the window on their desktop when the released .NET. Another window of opportunity could have been the open source release in the form of OpenJDK, but it did not make a major impact there either (with GNOME-Java in a constant state of flux and Jambi still in its infancy). The fact that Qt will be LGPL doesn't help.

Of course, it's still big as an application server and on some phones. And it will probably stay a while.

One real danger is that C# will replace Java as the education language if it can not keep up. As if it weren't bad enough to have C/C++/Pascal/LISP/whatever replaced ;) .

Edited 2009-02-20 22:17 UTC

Reply Parent Score: 3

RE[2]: Not unexpected
by vivainio on Sat 21st Feb 2009 16:47 in reply to "RE: Not unexpected"
vivainio Member since:
2008-12-26

They've done such a good job getting C++ easier and more productive that it reduces the appeal of higher level languages. I'm currently using PyQt quite a bit, and although it makes some stuff easier, my programs aren't really getting significantly easier or faster to develop. Some things are better in python, but you don't gain a huge amount.

Yeah, the UI layer code is pretty much the same in PyQt and C++ Qt. Where python really helps you is doing the (nontrivial) backend stuff.

We are living in interesting times... it may be that LGPL:ing Qt just saved C++ on desktop. Certainly the "managed" low level languages (Java & C#) lost much of their appeal, with 1) clunkiness and 2) platform lock-in working against them.

Reply Parent Score: 2