Re: We'll need a QT Jambi section!
Quote:
Originally Posted by
miketech
And I favor Java over Python
Poor you :) Maybe you'll walk out of darkness one day. :D
Quote:
Ok, I know the API of Qt, but there are many things in Qt I don't need again, because I have them already in Java.
Java is only a language and provides only the basics. Correct me if I'm wrong but things like SWING are not part of the language specification but rather an external component (a framework, like Qt is).
Quote:
In C++ it makes sence, because the standard doesn't offer many technologies. But in Java I already have sockets, threads, xml parsing ...
Many things will work better/faster than using "native" (look above) Java components, as a big part of them is compiled into binary and not interpreted. Apart from that, you can easily port C++/Qt code into QtJambi code and have a working Java-based application. Try "easily" porting SWING based code to C++.
Re: We'll need a QT Jambi section!
Quote:
Originally Posted by
wysota
Poor you :) Maybe you'll walk out of darkness one day. :D
Personally I like strongly typed programming languages. And if I wanna use a scripting language I favor ruby over python :)
Quote:
Java is only a language and provides only the basics. Correct me if I'm wrong but things like SWING are not part of the language specification but rather an external component (a framework, like Qt is).
Many things will work better/faster than using "native" (look above) Java components, as a big part of them is compiled into binary and not interpreted. Apart from that, you can easily port C++/Qt code into QtJambi code and have a working Java-based application. Try "easily" porting SWING based code to C++.
Hm, java isn't interpreted.
Imho it is only a matter of choice. Let's see what the future brings.
Greetings
Mike
Re: We'll need a QT Jambi section!
Quote:
Originally Posted by
miketech
Hm, java isn't interpreted.
Oh, really? That's something new... What CPU family do you use? AFAIK no current processor familiy runs java code natively - they all need a virtual machine... But hey, that's great news, if that's true maybe java applications will move from TurtleSpeed mode to CheetahSpeed mode soon!
Sorry for being ironic :)
Re: We'll need a QT Jambi section!
Quote:
Originally Posted by
miketech
Hm, java isn't interpreted.
Neither is it native code. It's compiled into byte code which must be run a virtual machine. Even with the JIT compiler, most of the program is still byte codes being interpreted in the virtual machine. You simply can't get the performance with Java that you can with native code.
