Firefox nightlies for Linux are now using Gtk+3

Post by mhogomchungu » Fri, Jul 24, 2015, 4:37 AM UTC

__david__ wrote: post #5

whoopdedo wrote: post #4

Earlier quoted context omitted.

"oh no" that Firefox is dropping support for a slightly older technology (again)? "oh no" that GTK2 is a sinking ship that everyone is fleeing from? or do you mean "oh no" that Firefox is going to be at the center of yet another incendiary (and ultimately fruitless) debate. Because I can agree that any one of those is a good reason to say "oh no".

I've been out of the gtk loop for a while now—I built a couple apps on gtk2 back in the day. What is wrong with gtk3? Why would this be controversial at all?

Post by mwfunk » Fri, Jul 24, 2015, 4:42 AM UTC

__david__ wrote: post #5

whoopdedo wrote: post #4

Earlier quoted context omitted.

"oh no" that Firefox is dropping support for a slightly older technology (again)? "oh no" that GTK2 is a sinking ship that everyone is fleeing from? or do you mean "oh no" that Firefox is going to be at the center of yet another incendiary (and ultimately fruitless) debate. Because I can agree that any one of those is a good reason to say "oh no".

I've been out of the gtk loop for a while now—I built a couple apps on gtk2 back in the day. What is wrong with gtk3? Why would this be controversial at all?

Post by chrismorgan » Fri, Jul 24, 2015, 4:56 AM UTC

Post by Scarbutt » Fri, Jul 24, 2015, 5:15 AM UTC

evmar wrote: post #16

Chrome used GTK2 as that was current at the time, and when we looked into GTK3 we concluded that it'd be a pain to target both simultaneously (the point of the new major version number is that the API changed) and that as long as we were supporting old distros (e.g. "Long Term Support" versions) we should keep GTK2. These days, those older versions are dying away, but Chrome doesn't use much GTK anyway. I wonder how…

Post by Redoubts » Fri, Jul 24, 2015, 5:30 AM UTC

Scarbutt wrote: post #17

evmar wrote: post #16

Chrome used GTK2 as that was current at the time, and when we looked into GTK3 we concluded that it'd be a pain to target both simultaneously (the point of the new major version number is that the API changed) and that as long as we were supporting old distros (e.g. "Long Term Support" versions) we should keep GTK2. These days, those older versions are dying away, but Chrome doesn't use much GTK anyway. I wonder how…

So Chrome has its own GUI toolkit?