At 16:06 2005-11-27, anufrii wrote:
The biggest challenge I am facing next week is that majority of the
audience is Perl-blind. So CPAN for them is just another 4-letter word.
So do some homework. You know what kinds of real-world problems you may
face, so look for solutions on CPAN and figure out a way to present it to
them. Slides? Demo/proof-of-concept?
The obvious arenas that makes Perl shine:
Databases: DBI (transparent connectivity to ), DBIx::Simple (simple SQL),
Class::DBI/DBIx::Class (no SQL)
Sysadmin: File::*, SSH, Win32::Admin*something*
Web: Mechanize (scraping), XML::* (parsing), Catalyst (if you would like to
leave the desktop app)
Windows: Win32::GUI, Win32::GuiTest, Win32::API, Win32::OLE, Win32::
I could go on, but you probably already know all this :)
To me the dividing issue is whether you anticipate the GUI app building to
be the bottleneck (which may or may not point to .Net), or the actual
problem solving (which supposedly points to Perl).
Presenting technical details such as "Perl compiler does this,
whereas VBS is processed like that, therefore Perl script is faster "
should make more sense, in addition to the factors mentioned in my
original message.
Performance doesn't seem to be an issue either way, from the way it sounds.
Related modules, if it is an issue:
Devel::Profile
Win32::API
Inline::C
etc.
/J
