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.
Thread beginning with comment 472464
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE: Meh
by moondevil on Tue 10th May 2011 07:25 UTC in reply to "Meh"
moondevil
Member since:
2005-07-08

As I already told you in another threads, in the IT world VM based environments + JIT are more valuable than the previous all native solutions.

The hardware allows it, and people prefer the productivity gains to the difficulty to deal with low level APIs.

Surely you can also create high level APIs in native languages, but no one seems to care about it.

It does not mean I agree with it, but it is the reality, and I doubt any of us will be able to change it.

Reply Parent Score: 2

RE[2]: Meh
by vivainio on Tue 10th May 2011 07:34 in reply to "RE: Meh"
vivainio Member since:
2008-12-26


The hardware allows it, and people prefer the productivity gains to the difficulty to deal with low level APIs.

Surely you can also create high level APIs in native languages, but no one seems to care about it.


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.

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).

Reply Parent Score: 3

RE[3]: Meh
by _txf_ on Tue 10th May 2011 09:09 in reply to "RE[2]: Meh"
_txf_ Member since:
2008-03-17

It's a much neater concept than e.g. with C# / Silverlight, where you are forced to write almost everything in C#


I should point out on the ui level silverlight is a pretty similar concept to QtQuick but uses XAML instead of javascript. From what I've seen of qtquick binding to the ui is not as intuitive as in silverlight.

I don't like javascript that much (probably due to lack of familiarity) but its syntax is far cleaner than XML (it gets worse when using a tool like expression blend as it literally vomits out XML tags).

Everything else is very true, but that has been the tradeoff with managed languages since forever...

Edited 2011-05-10 09:11 UTC

Reply Parent Score: 2

RE[3]: Meh
by Nelson on Tue 10th May 2011 13:27 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