I don't write Perl, but will agree that the CPAN package library is massive. Python does have a lot of modules available, but CPAN has been around for far longer and is just more mature. I haven't really run into many situations that Python won't work. If you need to interact with C++ you can SWIG the C++ and call it in Python.
Its a personal preference, but sometimes it can be based on what is used by others that you work with. If there are preferred languages for various reasons like common libraries and such then its best to go in that direction, the same applies to those who will also maintain this code. If your coworkers don't know Python, but know Perl, its best to go with Perl so that when things break they can fix them. I recommend finding a task you want to do, and writing that task in both Perl and Python and base your final decision on what works best for you. How you feel about the language, the documentation, the syntax, the modules that exist and how you interact with them, etc. If using a language is like punching yourself in the face every time it doesn't matter how great a language it is you aren't going to like using it. On Tue, Feb 15, 2011 at 11:45 AM, John R. Hogerhuis <jho...@pobox.com>wrote: > Agree. Perl, mainly because of the massive CPAN package library. > > -- John. > _______________________________________________ > LinuxUsers mailing list > LinuxUsers@socallinux.org > http://socallinux.org/cgi-bin/mailman/listinfo/linuxusers >
_______________________________________________ LinuxUsers mailing list LinuxUsers@socallinux.org http://socallinux.org/cgi-bin/mailman/listinfo/linuxusers