> However, the problem of programs with GUIs in perl is that they create > very huge programs that eat very much memory if the programs are complex > and need to use threads. > I've just abandoned a program in WxPerl (an RSS reader/Podcast > reader/TV/Radio listener) because when it had one thread it occupied 40 > MB of memory, and after adding each new thread, other 40 MB of memory > were occupied, so at 4 threads it used 160 MB of memory, and I needed to > add more threads for updating. How is it that wxPerl chews up so much memory? Or is it that you kept a lot of data in-memory? If so then that's not a failing of wxPerl.
I wonder what is the most complex app out there (free or commercial) written in wxPerl?
