in reply to Getting Fed Up with ActiveState
This has to be one of the most jaw-dropping threads I've ever seen on Perlmonks. Had the OS been some sort of Linux, and the vendor was some Linux vendor, the response would have been get yourself a C compiler and learn how to use CPAN.
Excuse me, but, why should it be any different here? Perl compiles with multiple versions of Visual C++, Borland C++, and MinGW, which are all free for the downloading. Does ActiveState have a monopoly on Windows Perl? I don't think so. On the other OS's mentioned, they either are distributed with a gcc, or gcc's or other C compilers are easily available.
What confuses me the most is that neither aliased or Class::BuildMethods require a C compiler. So
C:> cpan -i aliased
should work just fine to install the modules. Previous threads by crazyinsomniac can provide you with the code needed to generate the nice HTML doc's that come with ActiveState, or you could just use "perldoc", but I'll let you make that call.
Unfortunately, the statement that troubles me the most is "Perl on Windows is crippled due to poor support." If that statement weren't so baseless, it would be insulting to the many people who have provided several thousands of hours of free programming and support to get Perl to work on Windows. Those people aren't just ActiveState, but also many of the people responding to this thread. Oddly enough, Perl has compiled and run on Windows for years, and will continue to do so for years to come. Much like all the other OS's supported by Perl, it routinely passes the 170,000+ test cases on a daily basis. As has been said elsewhere, Perl is everywhere. Just to let you know, that includes Windows.