osnews.com — Google initially thought that a Windows clone would be acceptable, since Chrome itself is already such a fast application. However, the people working on the Linux version of Chrome made a case for using Gtk+ instead, and Google went with that option.
Feb 14, 2009 View in Crawl 4
alexweejFeb 15, 2009
If Firefox was really GTK it might actually be good.
nalf38Feb 16, 2009
I don't give a rat's ass if it's ported with WINE, just stop bitching about it and f**king do it already. Why suddenly all this concern over appearance? Picasa and Google Earth both look like complete s**t on Linux and we still use them. Hey, maybe Google could contribute a halfway decent looking window/button theme for WINE that doesn't look like it just got crapped out of 1995's ass.
canolucasMar 4, 2009
my opinion: they have to use the ugly GTK+ because they don't want to depend on a toolkit owned by it's competitor nokia..
eruaranMar 31, 2009
Yes, I can have my Qt front end for VLC, and I can have my Qt front end (and beautiful integration with System Settings) with KPackageKit. Even if Google said, "here's the back end, you guys knock yourselves out making a Qt or GTK front end or whatever", we know plenty of people would oblige.
eruaranMar 31, 2009
Qt 4.5.That is all.
bugmenotttJan 27, 2010
Forget mousepad. Leafpad is an alternative with a heck of a lot fewer dependencies and no functionality loss. I honestly don't know why you need xfce dependencies for a text editor. The problem of desktop environment dependencies for simple GUI programs is huge and I couldn't agree more that it's one of the largest issues on linux systems today. g[tk]whatever and q[t]whatever for the win; gnomewhatever and kwhatever for the lose.