Why gtk+ application are so slow

[Victor Nazarov <vir comtv ru>]

I'm using Debian every day... And I've been trying to find why I prefer 
MS Widows GUI over Gnome. Now I've undesrtood. It's responsiveness. So I 
know that gtk+ is superior over Win32 becouse of it's portabillity and 
the most important is the ease of programming with it. But Gnome and GTK 
applications are considerably slower than Win32 applications. The time 
betwean the execution of application and the creation of the 
application's main window is very long... So I'd like to hear some 
opinions why is it so? I don't like to buy new, /modern/ computer, I 
want Gnome to work as fast as Windows 2000 does...

Here is my opinion: I think  the main problem is that gtk prefer 
run-time over compile time... So programmer binds callbacks on signals 
at run time... In win32 the compiler does it when compils WinProc 
functions switch statement... There are many other such examples. But I 
like gtk API and I don't whant to use clumsy Win32 API. IMHO it's not a 
good idea to separate application code from the description of user 
interface (separated XML file for example). So I suggest to write a 
preprocessor for the gtk interface, something like yacc... So different 
statements of the preprocessed language will generate an array that will 
represents a whole window with all the widgets properly initialized, 
only some small subset of data, depending on the execution environment 
will be initialized at run-time. The task of the main function will only 
initialize minimum fields of array representing the window, point some 
gtk function to this array and run gtk_main... What do you think about 
this proposal?

--
vir