When I was younger, Perl used to be the language of choice for Unix system and network programming: when one didn't want to bother writing in C, Perl could do everything with a lighter syntax and less time wasted on the irrelevant.
Nowadays, network programming necessarily involves IPv6 (the current IP version), and while Perl supports it (there is a Socket6 module), (1) it's not part of the core language / module set, (2) it doesn't seem to interact too well with the core modules, and (3) it doesn't have nearly all that is necessary for socket manipulation, and it seems pretty much abandoned.
The problem with (1) is that even if the module is on CPAN, it is not guaranteed to be available everywhere where Perl is, and installing it can be a problem. This is absurd: in 2014, IPv6 is not an advanced feature that can afford to be optional, it makes no sense for Perl not to have native IPv6 support.
The problem with (2) is illustrated by the following trivial script:
#! /usr/bin/perl -w
use strict;
use warnings;
use Socket;
use Socket6;
which produces the following output:
Subroutine main::pack_sockaddr_in6 redefined at /usr/share/perl/5.14/Exporter.pm line 67.
at /tmp/stupid.pl line 5
Subroutine main::unpack_sockaddr_in6 redefined at /usr/share/perl/5.14/Exporter.pm line 67.
at /tmp/stupid.pl line 5
Subroutine main::sockaddr_in6 redefined at /usr/share/perl/5.14/Exporter.pm line 67.
at /tmp/stupid.pl line 5
Note that calling use Socket and use Socket6 (with no list of exports and in that order) is recommended by the official Socket6 documentation, I didn't invent it. While these are only warnings (and can be disabled by removing the -w switch), is still goes to show that Socket and Socket6 are not perfectly well integrated.
As for (3), it is illustrated by this bug report which I opened nearly four years ago, with a patch and which drew exactly zero response during that time. It is simply impossible to reliably open a socket without having the IPV6_V6ONLY constant because Unix systems disagree as to the default value.
I have the feeling that these are all symptoms of a larger picture, namely that Perl5 is pretty much abandoned. Which I think is very sad, because there is no other language that can claim to occupy the niche where Perl5 sits (or sat).
Can someone offer hope?