●Stories
●Firehose
●All
●Popular
●Polls
●Software
●Thought Leadership
Submit
●
Login
●or
●
Sign up
●Topics:
●Devices
●Build
●Entertainment
●Technology
●Open Source
●Science
●YRO
●Follow us:
●RSS
●Facebook
●LinkedIn
●Twitter
●
Youtube
●
Mastodon
●Bluesky
Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!
Forgot your password?
Close
This discussion has been archived.
No new comments can be posted.
Load 500 More Comments
Full
Abbreviated
Hidden
/Sea
Score:
5
4
3
2
1
0
-1
More
Login
Forgot your password?
Close
Close
Log In/Create an Account
●
All
●
Insightful
●
Informative
●
Interesting
●
Funny
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
byDarkness404 ( 1287218 ) writes:
Seriously Google how hard can it be? Just use GTK, its light, useful and even a weekend coder can use it.
byAnonymous Coward writes:
Meh, everything is a trade-off. Qt is way easier than Gtk and has a huge API for doing all sorts of cross-platform stuff. Plus it's truly cross-platform whereas Gtk is pretty crappy on anything other that systems running X Windows.
The trade-off is that Qt is C++ and Gtk is C. This actually matters a lot when you need to interface to other C-only applications and libraries or whatever. C++-to-C is easy but using it the other way around is problematic and annoying. Then you have the issue of how clean th
byEsbenMoseHansen ( 731150 ) writes:
Meh, everything is a trade-off. Qt is way easier than Gtk and has a huge API for doing all sorts of cross-platform stuff. Plus it's truly cross-platform whereas Gtk is pretty crappy on anything other that systems running X Windows.
The trade-off is that Qt is C++ and Gtk is C.
Well, considering that Chrome is based on freaking fork of KHTML (Webkit), both of which are written in --- you guessed it --- C++, interfacing to C++ is hardly an issue. Chrome is most likely written in C++ --- or at least, this is indicated by Wikipedia. A more likely reason was that when Google started on their (closed-sourced?) browser, Qt was still only available for money or GPL, and they preferred the cheaper GTK option.
byNarishma ( 822073 ) writes:
As they explained multiple times, they choose GTK because that's what the team doing the Linux "port" is familiar with. However their architecture allows to easily use different toolkits and they are willing to accept patches to support Qt or whatever else. They just don't have the resources necessary to support more than one toolkit.
byEsbenMoseHansen ( 731150 ) writes:
As they explained multiple times, they choose GTK because that's what the team doing the Linux "port" is familiar with. However their architecture allows to easily use different toolkits and they are willing to accept patches to support Qt or whatever else. They just don't have the resources necessary to support more than one toolkit.
For laughing out loud. Just like SWT supports any toolkit, I presume. What they did was to shove an abstract API mirroring the one of the windows toolkits. Of course, you can make that work on any toolkit, but it is not always going to be easy, nor a perfect match. And who needs another browser? Chrome offers very little new, being essentially Yet Another Konqueror Fork. (Maybe we can just label them all YAKF :o) )
But I merely replied because of the stupidness spouted about C++ re Qt.
Parent
twitter
facebook
●threshold.
There may be more comments in this discussion. Without JavaScript enabled, you might want to turn on Classic Discussion System in your preferences instead.
Slashdot
●
●
Submit Story
It is much harder to find a job than to keep one.
●FAQ
●Story Archive
●Hall of Fame
●Advertising
●Terms
●Privacy Statement
●About
●Feedback
●Mobile View
●Blog
Do Not Sell or Share My Personal Information
Copyright © 2026 Slashdot Media. All Rights Reserved.
×
Close
Working...
Working...