My favourite GUI is a web browser. If you create your program web-based, you can let multiple people use it, and eventually maybe put it online as a public service. Most of my scripts are in a way web based, but I enjoy creating modules as well. When my program is not web-based, it is probably a quick hack (perhaps a command line interface for a web based application).

A while ago, I wanted to create a simple IRC bot framework, but in the process of creating it, I needed some output, and turned it into a web page for easy markup. I needed input too, so I created some UDP interface for that, and that got a simple web based form so I didn't have to use netcat. A while later, I had it output user lists, to see if my mode hashes were correct. Without really realising it, I created a CGI webchat instead of the IRC bot framework. Oops :)

Yes, I'm obsessed with web based programming with Perl. But "web based" does not equal "simple minded", or imply stupid solutions.

How about...

• Design patterns: how to create a consistent GUI application without event loops?
• The future: will Perl 6 be as easy to intergrate in a webserver as Perl 5 is? Will it be able to re-execute package code (so scripts no longer have to be inside subs to cache them)?
• Dynamic perl: templates? autoloading tag subs? dynamic GUI layout?
• Enterprise architectures: what's the back end for the CGI scripts?
• Natural language: can we determine what the (obviously clueless :-)) websurfer tries to tell?
• Automatic installation: when will the first web based CPANPLUS shell be made?

Yes, I reinvent wheels.