note
g00n
<ul>
<li>GUI: use for cross platform *native* gui client side development - (only if you think <a href="http://www.scriptics.com/software/tcltk/8.0.html">Tk</a> is the best you can do.)<br>
<li>PPM: use for gui client side development on MS Windows using CPAN - (because <a href="http://www.google.com/search?q=activestate+ppd&sourceid=mozilla-search&start=0&start=0&ie=utf-8&oe=utf-8">ActiveState ppm</a> is horribly broken and you cant utilise CPAN.<br>
<li>Shipping: problems with MS Windows GUI/Perl apps when shipping - (because existing tools are bloated, proprietary).
</ul>
<p>I am ambivalent about using Perl for <a
href="http://www.google.com/search?num=100&hl=en&lr=&ie=UTF-8&oe=UTF-8&q=perl+gui&btnG=Search">client
side *native* gui programming</a>.</p>
<p>There is a great article by <a href="http://www.oreillynet.com/pub/au/110">Eric Burke</a> on
<a href="http://www.oreillynet.com/pub/wlg/4649">why GUI programming is hard</a> that sums up why nicely -
namely <em>server side development (with languages like Perl) allow for automation once the design problem(s)
can be defined</em>.</p>
<p>Gui development on the otherhand, <em>cannot be automated as easily</em>. The other thing the <em>mismatch between
skill sets between server side and gui client developers</em>.</p>
<p>I would also be interested to know who develops gui apps <em>aside from MS Windows</em>? Any commercial apps or are they all inhouse? How do you ship? What front end do you use?</p>
<em>update:</em> sp.
346790
346790