Hi Sven
I have just done some digging into the history of Java and Qt, and was
surprised to find that Qt is longer in the tooth than I had thought.
Interestingly both Qt and Java emerged at roughly the same time.
Trolltech [1] starting to write Qt in 1991. The earliest date I can
find for a release [2] is 1998 for 1.4.0
Java [3] development also started in 1991, and was first released in 1995.
Thus at the start of Qt development, Java was either not available at
all, or at best just a promise of things to come, and very far from
the obvious choice that it might seem today.
Chris
[1] http://en.wikipedia.org/wiki/Trolltech
[2] http://no.wikipedia.org/wiki/Qt
[3] http://en.wikipedia.org/wiki/Java_(programming_language)
Zitat von "Sven Putze" <sailfish...@hardcodes.de>:
The interesting question is, why did the original creators of Qt
opt for C++, rather than the more obvious Java? I suspect that the
answer is in the multi-platform ethos of Qt. Quite simply there is
an open source C++ compiler available for almost any architecture
you can think off, which is not the case for Java, especially in
the mobile arena.
Hi,
there was no Java available at the time when Qt was created. And
when Java came out, the desktop computers were much slower/smaller,
so keep on using C++ to create fast native code was a natural
choice. Quite the same situation with those small tiny computers we
use to put in our pockets today. There is still a need for fast
native code if you think in terms like performance or power usage
(=battery life).
But hey, I am no preacher of the church of C++.
If people want to use Python, they should. They "only" must put
everything needed inside their app.
BR.
Sven
_______________________________________________
SailfishOS.org Devel mailing list
_______________________________________________
SailfishOS.org Devel mailing list
