Linked by Thom Holwerda on Mon 9th May 2011 21:14 UTC, submitted by Elv13
Qt Since Nokia announced its switch to Windows Phone 7, people have been worried about the future of Qt. Well, it turns out Nokia is still going full steam ahead with Qt, since it has just announced the plans for Qt 5. Some major changes are afoot code and functionality-wise, but the biggest change is that Qt 5 will be developed out in the open from day one (unlike Qt 4). There will be no distinction between a Nokia developer or third party developer.
Permalink for comment 472544
To read all comments associated with this story, please click here.
RE[3]: Meh
by Nelson on Tue 10th May 2011 13:27 UTC in reply to "RE[2]: Meh"
Nelson
Member since:
2005-11-29


QML sort of lets you have your cake and eat it too. You have full access to the native platform on "metal" level (C++ & Qt), while allowing you to write as much of the code in "scripted" environment on QML side.


I don't see how you're eating your cake too, when Javascript is a typeless language, which can lead to all sorts of weird quirks when unexpected things happen.


It's a much neater concept than e.g. with C# / Silverlight, where you are forced to write almost everything in C# - and C#/CLR is still not "low level enough" when you really want that (to conserve RAM, hand tuning the algorithms to optimize cpu cache use, whatever).


I don't know, the CoreCLR in Silverlight 5 is pretty damn fast now and is still tiny. In fact, last time I checked, the CLR's JIT engine still outperformed Javascript JIT engines.

If most of the time is spent in QML/Javascript, I don't see how you can claim the performance benefits of being "closer to the metal" while using an interpreted/JIT'd language.

I'm not sure if QML is interpreted or if its compiled to an intermediary language (XAML on WPF is compiled to BAML a binary representation, and XAML on Silverlight is interpreted)

Reply Parent Score: 2