Live data from Hacker News

Ask HN: Time to give up on Qt?

news.ycombinator.com

21–30 of 72 posts

Re: Ask HN: Time to give up on Qt?

#22

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.

Yeah, I agree with this. I still like seeing the discussion here, since I'll concede that there may be some special circumstances and constraints that lead a developer or team to go with one of these cross-platform UI toolkits, but I think on the whole people are better off picking a platform and creating a truly native experience, including exploiting the unique strengths of the platform. Same goes for the cross-platform frameworks available for iOS, Android, etc.

Re: Ask HN: Time to give up on Qt?

#23
post #20

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.

> The only viable cross-platform is the web. Yeah with its mixture of CSS/HTML/JavaScript crap that works perfectly across all browsers versions and operating systems.

Use toolkits like Extjs, which provide a rich palette of widgets and hide away incompatibilities. http://www.sencha.com/products/extjs/

Re: Ask HN: Time to give up on Qt?

#24

Qt is probably pretty hard to beat in maturity, but http://www.cocotron.org/ looks like an interesting project, allowing you to build your OS X applications for other platforms (Windows, Linux).

I would love to see Cocotron do well, but the last post on the blog is: Wednesday, December 22, 2010 - Cocotron is alive and kicking

But their codebase seems recent: http://code.google.com/p/cocotron/source/list

Re: Ask HN: Time to give up on Qt?

#26
Qt is the best cross-plataform GUI Toolkit.

But it still feels odd on Windows, and OSX, and Linux (provided that most Linux users are on Gnome these days).

I would rather spend twice the time coding it for native Windows forms and OSX Cocoa.

Re: Ask HN: Time to give up on Qt?

#27
post #20

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.

> The only viable cross-platform is the web. Yeah with its mixture of CSS/HTML/JavaScript crap that works perfectly across all browsers versions and operating systems.

If the problems with that "crap" were insurmountable we wouldn't have the huge variety of websites like we do today. And I would argue that just as big cross platform issues exist with Qt/Swing.

With Modernizr, JQuery etc you can get 95+% of the features on 95+% of computers.

Re: Ask HN: Time to give up on Qt?

#28
post #20

Earlier quoted context omitted.

> The only viable cross-platform is the web. Yeah with its mixture of CSS/HTML/JavaScript crap that works perfectly across all browsers versions and operating systems.

Use toolkits like Extjs, which provide a rich palette of widgets and hide away incompatibilities. http://www.sencha.com/products/extjs/

You realize the Qt basically does exactly that for non-web apps except it's far more comprehensive and tested, right?

Re: Ask HN: Time to give up on Qt?

#29
post #26

Qt is the best cross-plataform GUI Toolkit. But it still feels odd on Windows, and OSX, and Linux (provided that most Linux users are on Gnome these days). I would rather spend twice the time coding it for native Windows forms and OSX Cocoa.

Provided enough resources I think the best approach is writing a library in C/C++ for the core and then using the native toolkit for the GUI.

Transmission does this and it's beautiful both on OS X and Gnome. Adium does something similar and it's a good mac app.

Post reply on HN