To view parent comment, click here.
To read all comments associated with this story, please click here.
If they wanted familiarity, they would've chosen C#
Bad idea. The woes of Google with Dalvik and Java should teach anyone to avoid encumbered development technologies, especially in the crazy mobile sphere. If Java has a shadow of Oracle behind it, C# has a shadow of Microsoft attached. While Sun encouraged Google to use Java, Oracle isn't Sun. So even if Microsoft wouldn't mind now, you never know where their rights over C# will end up tomorrow, or even if they'll just change their mind. It just doesn't worth the risk.
Edited 2013-01-02 23:51 UTC
C# is an open specification, so are large parts of .NET.
What Google did to Oracle to Java at the LEAST is highly unethical and appalling from a company that claims to do no evil. They likely would've had an easier time working with the Mono team.
Seriously, C# is everywhere, people have been saying that Microsoft will become aggressive any day now over .NET since 2001
Actually all the QML-like technologies (JavaFX and XAML as far as I remember) are very immature pieces of technology yet, but they are already in production.
But I completely disagree with the Qt part. Qt is one of the best and most mature UI frameworks available right now (IMHO next to Java Swing). Qt is by far the best C++ UI framework (more powerful, easier to learn and portable than, say, MFC, WTL, wxWidgets or the old VCL) and the best portable UI framework.
The Qt portfolio is very nice, AFAIK: Google Earth, Perforce Client, Adobe Elements, the KDE desktop, KOffice, Swipe Nokia N9 UI use it with success.
QML to me had very elementary limitations that showed that it hasn't been put through its paces. Things that I've taken for granted in XAML are not present in QML.
For example QML has states, but no concept of state groups, so its impossible to have states which are not mutually exclusive co-exist within a view.
That, and I think a lot of the C++ and JS and even the Signal and Slot integration is pretty clumsy.
XAML falls on its face in a few regards here too, but XAML has well developed frameworks to show people how to use it the right way.
Not saying that QML is fundamentally bad, it is the best thing to happen to Linux, I just don't know if its ready for prime time yet.
I do love the JSON-ish syntax over XML. XAML is way too verbose.
But I completely disagree with the Qt part. Qt is one of the best and most mature UI frameworks available right now (IMHO next to Java Swing). Qt is by far the best C++ UI framework (more powerful, easier to learn and portable than, say, MFC, WTL, wxWidgets or the old VCL) and the best portable UI framework.
I can concede that, I'm sure you have more experience with it than me.
Qt is also used by
- Autodesk Maya [8][9]
- Skype
- VLC media player [10]
- VirtualBox
- Mathematica [11]
- the European Space Agency [12]
- DreamWorks [13][14]
- HP [15]
- The Foundry's Nuke [16]
- Lucasfilm [17]
- Panasonic [18]
- Philips [19]
- Samsung [20]
- Siemens [21]
- Volvo [22]
- Walt Disney Animation Studios[23]
- RIM (Research In Motion) [24]
[8] http://web.archive.org/web/20110723145736/qt.nokia.com/qt-in-use/au...
[9] http://web.archive.org/web/20110723145736/qt.nokia.com/qt-in-use/qt...
[10] http://qt.digia.com/Qt-in-Action/VLC-media-player/
[11] http://qt.digia.com/Qt-in-Action/Mathematica-by-Wolfram-Research/
[12] web.archive.org/web/20110723145813/qt.nokia.com/qt-in-use/story/custom er/esa-european-space-agency
[13] http://qt-project.org/videos/watch/behind_the_scenes_at_dreamworks_...
[14] http://qt-project.org/videos/watch/ui_system_design_challenges_for_...
[15] http://qt-project.org/videos/watch/developing_innovative_desktop_an...
[16] http://qt.digia.com/Qt-in-Action/The-Foundry/
[17] http://qt.nokia.com/qt-in-use/story/app/lucasfilm-entertainment-com...
[18] http://web.archive.org/web/20110723145947/qt.nokia.com/about/news/p...
[19] http://web.archive.org/web/20110723145930/qt.nokia.com/qt-in-use/qt...
[20] http://web.archive.org/web/20110723145854/qt.nokia.com/qt-in-use/qt...
[21] http://web.archive.org/web/20110714191438/qt.nokia.com/qt-in-use/st...
[22] http://qt.nokia.com/qt-in-use/story/customer/volvo-mobility-systems
[23] http://qt.nokia.com/qt-in-use/story/customer/walt-disney-feature-an...
[24] http://blog.qt.nokia.com/2011/11/17/new-keynotes-rim-and-community-...
There's quality in Qt.
Edited 2013-01-03 11:39 UTC
I agree. XAML is however an open specification and people are free to implement it. Not that I think they should. I like QML's approach a little better. Immature does not mean bad in my opinion, just needing of some more incubation.
XAML's XML long syntax is getting long in the tooth and it seems like its just a DSL made for tooling rather than for developers to write.
I'd love a decent .NET Toolkit with QML (or a QML like) declarative UI markup language and from someone who's learned lessons from the XAML platforms.





Member since:
2005-11-29
If they wanted familiarity, they would've chosen C# which has broad cross platform support:
Windows Phone 7, 8, Windows XP - 7, Windows 8 (Desktop and Metro), iOS, Android, PS3, PS Vita, Linux, OSX, etc.
It is a higher level more productive language, safer, and with a richer set of tooling.
Qt is nice, but Qt and especially QML are very immature pieces of technology yet.