I think Jason have three different decision to make not one.
in reply to Why GUI perl programs on Windows?
Thinking of them combined as just one decision is misleading.
- Whether or not to use Perl?
- Which GUI Tool Kit to use?
- Whether or not he should go with a tradiotional GUI in the first place? As opposed to a CLI (command line interface) or a Web-UI
In theory Perl should not dependent on any one GUI/TK (graphical user interface tool kit), but of course I know that in practice some binding will be more complete than others but in that case we would be complaining about this particular gui binding module, and not Perl in general.
You should or not choose Perl, based on one the general qualities of Perl, two the quality GUI Lib bindings
The same rule (language independence) may apply to the GUI/TK, but thinking about it for a while, but it really doens't have too, like in the case of TK, it relies on the Tcl style of programming. Any computer language is ultimately a textual user interface that support some programming paradigm a GUI/Tk may be writen to take advantage of a certain paradigm, if the language doesn't support this paradigm, I would expect trouble in creating the binding, and api maping
Last, are you even sure you want a GUI, did you consider a WebUI.
I think those three decision are better made in the reverse order in which I discussed them, first decided what type of interface you want, next if you decided to go with a traditional GUI pick the Lib or ToolKit, last choose the language which best suite the lib programming style.