It's time to give up _cross-platform_. Doesn't work well with the increasingly different UX concepts of different platforms anyway. The only viable cross-platform is the web.
Ask HN: Time to give up on Qt?
41–50 of 72 posts
Re: Ask HN: Time to give up on Qt?
#42It's time to give up _cross-platform_. Doesn't work well with the increasingly different UX concepts of different platforms anyway. The only viable cross-platform is the web.
Developing interfaces in html/js even factoring the added IE crap is a breeze compared to C++ development. Even with Qt sanding a lot of rough patches
Not that C++ per se is too complicated, rather, building an interface in C++ and doing "a desktop application" with it is a complex task, something that the web model was made to do
Now, for something like a headless application, C++ is fine (and of course it's harder than Python, but not a lot with STL, etc)
Re: Ask HN: Time to give up on Qt?
#43It's time to give up _cross-platform_. Doesn't work well with the increasingly different UX concepts of different platforms anyway. The only viable cross-platform is the web.
I''m sure Autodesk, Virtualbox, Google Earth, Mathematica, VLC, Transmission, Scribus, Skype, etc, etc would be very interested to hear how unviable they are.
Re: Ask HN: Time to give up on Qt?
#44Re: Ask HN: Time to give up on Qt?
#45I was interested to see the claim that the dropbox client uses wxWidgets (actually wxPython) on this page: http://www.wxwidgets.org/
I don't see any obvious sign of wxPython in there, though. Nothing with "wx" in the name, for example.
Re: Ask HN: Time to give up on Qt?
#46It's time to give up _cross-platform_. Doesn't work well with the increasingly different UX concepts of different platforms anyway. The only viable cross-platform is the web.
I must ask because this just looks like webapp kool-aid. I am increasing my own investment in webdev and I still completely disagree with you.
Re: Ask HN: Time to give up on Qt?
#47Earlier quoted context omitted.
I''m sure Autodesk, Virtualbox, Google Earth, Mathematica, VLC, Transmission, Scribus, Skype, etc, etc would be very interested to hear how unviable they are.
All of them were started in the past, when desktop programming was still considered a good thing.
Re: Ask HN: Time to give up on Qt?
#48Earlier quoted context omitted.
I''m sure Autodesk, Virtualbox, Google Earth, Mathematica, VLC, Transmission, Scribus, Skype, etc, etc would be very interested to hear how unviable they are.
All of them were started in the past, when desktop programming was still considered a good thing.
Re: Ask HN: Time to give up on Qt?
#49It's time to give up _cross-platform_. Doesn't work well with the increasingly different UX concepts of different platforms anyway. The only viable cross-platform is the web.
The thing is, C++ is hard Developing interfaces in html/js even factoring the added IE crap is a breeze compared to C++ development. Even with Qt sanding a lot of rough patches Not that C++ per se is too complicated, rather, building an interface in C++ and doing "a desktop application" with it is a complex task, something that the web model was made to do Now, for something like a headless application, C++ is fine (…
The caveat at present is that the standard desktop widgets are not yet fully available from QML (see [1] for a recent update). For most of my application this doesn't matter (I haven't decided how I'll do the settings dialog yet), but for enterprise apps it quite likely does.
[1] http://labs.qt.nokia.com/2012/06/06/desktop-components-for-q...