any detailed info on GTK+ plans?

> The article mentioned cruft, and it's a natural assumption that there's 
likely to be speed gains in ditching it.  How much -- who knows?

Anything performance related should be backed up with test-case(s), 
numbers and conclusions based on those numbers, everything else is bound 
to be dead wrong.


> Honestly, the only speed impact I really notice from GTK+ is when 
firefox is rendering a particularly complex web page in a backgrounded 
tab, bringing the current tab essentially to a halt.

I don't think this has anything to do with Gtk.  Firefox doesn't use
Gtk to draw www-page content (for obvious reasons, Gtk widgets are quite 
different from www-form widgets) and if it's in background tab, there 
isn't even anything to draw.  I think it's more to do with JavaScript &  
Flash content (Flash doesn't use Gtk either), CSS and complex page 
layout / layering.  Firefox has all tabs in same process (to save memory I 
assume) and AFAIK doesn't really thread its work that much.